#99 - Setting permissions for usergroups rather than for content
| Identifier | #99 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Setting permissions for usergroups rather than for content |
| Status | Completed |
| Tags |
Roadmap: Sponsorship (custom) Type: Usability (major) (custom) |
| Handling member | Chris Graham |
| Addon | core_permission_management |
| Description | e.g.
<pre> Edit Super-moderators ===================== Forums ------ Item | Perm 1 | Perm 2 Root | x | o -General chat | x | o --Boring place | o | x -Feedback | x | o Downloads --------- ... </pre> Going into theory territory, the permissions model is basically 3d, with 3 axes:<ul> <li>Usergroup <li>Permission (e.g. submit-mid, edit-low, double-post, …) <li>Content item </ul> The points represent "on" or "off" or "inherited" or "n/a" permissions. We currently allow choosing of a content item plane and then setting a usergroup/permission matrix from it. This new feature would allow choosing of a usergroup plane and then setting a permission/content-item matrix from it. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
This feature is about making permissions easier to set, not making new permissions.
There is already a feature for invisible logins, although it needs enabling via the "Enable invisible log-in" option. It won't make them anonymous though, only invisible on online-user lists.
When posting on the forum in v10+ there is an option to allow members to post in forums anonymously - this is set per-forum). There's no option on the comment form though (I'll add an issue for that).
In both these cases it's not a privilege thing, it's a choice thing. I don't think the majority of users would need to restrict invisibility/anonymous as a permission.
If you want to change your sponsorship after seeing this information let me know. You can probably adjust it yourself on here but I've not tested that.
It took a long time to get to this, due to the big development backlog with already planned v11 features, sorry for the delay in getting everything done. Hopefully it won't be too much longer now.