Permissions

Summary

Should we have a policy of creating new permissions so that things mean what they say, rather than leveraging existing and often obliquely related ones?
- site.upd issues for flexibility of delegation

[From Clay:]

Rather than taking site.upd as a broad authority for all tools in a given site, each tool (or at least each tool which provides some site maintainer options) should have its own <tool>.upd (or perhaps <tool>.admin is better) permission.
Site Info permissions should be more fine-grained. The tool comprises a fairly broad set of site management pieces, some of which could be appropriate for TAs/Tutors to manage while at the same time constraining their access to others.

{From John L.}

Should there be an item on the checklist for tools moving from provisional to core that includes permission handling consistent with other tools in Sakai? Some tools have a permission page, some don't, some were setting them in properties, etc.
Need to revise the permission page UI to handle group control