By judah on
I see a lot of people, including myself, are constantly asking for permissions for this and permissions for that. What do you say to a module level permissions standard?
We could require (loosely as a version 2.0 requirement) that modules pass their features through the permissions page or alternatively modules create a standard permissions page for all of their features. It may be a little more work up front but then we would cut down on half the feature requests posts and fulfill many wishes at the same time. X's represent checkboxes.
| Module | Anonymous | Authenticated | Content Creator | Administrator |
| Node | ||||
| - Custom | X | X | X | |
| - Add | X | X | X | X |
| - Edit Own | X | X | X | |
| - Edit All | X | X | ||
| - Delete | X | |||
| - Allow Drafts (Private Nodes) | X | X | X | |
| - Allow Images | X | X | X | |
| - Allow Signitures | X | X | X |
Comments
Taxonomy-based Permissions
If you are coming up with a list, permissions based on a taxonomy would be nice also.