Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Input needed: How would you organize Confluence space permissions on one screen?

Chelsea Wan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 7, 2025

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:image-20251107-203921.png

In particular, we’re interested in your responses to the following questions, as well as any general thoughts:

  1. Which set of groupings feels more intuitive? Which is easier for you to parse and understand a user’s access?

  2. Is any of the language in these screens confusing to you?

  3. 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!

4 comments

Comment

Log in or Sign up to comment
Hanna Torany
Contributor
November 7, 2025

Hi,

  1. Option A is easier and more organized
  2. No
  3. It looks good in option A

For us the most important part that the Space Admins can see the restricted pages under the Content Manager

Like # people like this
Tami Dubi
Contributor
November 9, 2025

HI @Chelsea Wan ,
Option A has more categories, making it easier to work with. 

 

Like Chelsea Wan likes this
Fabio Müller
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 9, 2025

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!

 

 

Like Chelsea Wan likes this
Alexander Ruetzler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 9, 2025

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.

Like Chelsea Wan likes this
TAGS
AUG Leaders

Atlassian Community Events