Hi everyone! I’m Chelsea, a content designer on the Confluence Permissions team.
We’d like your input on how to organize permissions information for easy understanding in our new role-based space access experience. Here are 2 versions of a screen that shows which permissions are included in a given role:
In particular, we’re interested in your responses to the following questions, as well as any general thoughts:
Which set of groupings feels more intuitive? Which is easier for you to parse and understand a user’s access?
Is any of the language in these screens confusing to you?
Is there an ordering of permissions within each grouping that makes sense to you?
The more context you can give for your answers, the better!
Thank you!
Hi Chelsea,
the first option looks more intuitive to me. The categories there help a lot compared to option b.
Looking forward to those changes!
For our company, which requires stricter permission controls, option A is preferable. Its UI is also more intuitive compared to option B.
However, we would like to see both "Content Manager" and "Automations" become their own distinct roles in the permissions model. Currently, automation features are only accessible through the Admin Role, which also grants the ability to delete spaces—something we must restrict for auditing purposes.
Internally, we use a role-based access control (RBAC) system and cannot allow users to have the Admin Role just to access automations or advanced content management functions. Distinct roles for "Content Manager" and "Automations" would offer greater flexibility and security in assigning permissions. There is already a feature request for -->[CONFCLOUD-83084] Enhance RBAC: Split Automation & Analytics Permissions from “Manage Everything in this Space” (Space Admin) in Confluence - Create and track feature requests for Atlassian products.