📣 Early Access: Improved space access management with new Confluence roles

[#1]

Hello Confluence Community, 

We’re excited to share a new way to manage space access in Confluence — using roles! You’re invited to join our Early Access Program (EAP) and be among the first customers to explore and provide feedback on this new feature.

Sign up for the EAP now ➡️

Roles make managing user access more consistent, predictable, and scalable. Each role has a different set of individual permissions associated with it, giving admins confidence in what each user can do.

Say goodbye to cognitive overload with the current granular permissions table in Confluence, and hello to improved user management with roles!

Here’s what you can expect...

Simply choose a role

Within the Users table, the 14 individual permissions checkboxes (😱) to assign access to each user will be replaced with a single role selector. You’ll see this change in both individual Confluence spaces and Default space permissions (which are applied to all new spaces). Learn more about Confluence roles.

View each role’s individual permissions

From the Users table, you can easily audit all permissions associated with a role and make changes if necessary. 

Automatic role assignment

When this experience arrives, all users whose current permissions map directly to one of the new roles will automatically be assigned the role, so you don’t have to.

All users whose permissions don’t directly match a role will retain their permissions and be described as having “Custom access”. You can switch them onto a role at any time.

Assign roles to user classes to manage access at scale

Assign roles broadly to different classes of users like All Confluence users or All Confluence admins, regardless of group membership. These sit alongside user groups and will start with no access by default.

Manage it all from a single screen

Instead of three separate tables to manage permissions for users, groups, and guests, you now have a complete view of access on one screen.

How to join the EAP

➡️ Sign up today for exclusive access to the new role-based space access management experience.

Please note: In order to participate, you’ll need a site admin or organization admin on your Confluence site to sign up for this EAP. Interested in the Early Access Program, but not an admin? Message your admin to sign up!

EAP program details and eligibility

• The EAP is set to launch around November 20, 2024.
• Customers on Standard, Premium, and Enterprise editions of Confluence are welcome to participate.
• In order to participate, you’ll need a site admin or organization admin on your Confluence site to sign up for this EAP.
• We will limit the number of participants for this EAP so that we can properly manage the feedback that comes in as part of it and will reach out to your team if you’ve been accepted into the program.
• Throughout the EAP, we will use a private community group to communicate with all participants. We ask that you provide feedback on the feature and insights about your experience, including about usability and performance.

We are committed to making managing permissions in Confluence using roles the best it can be, and we are eager to receive your valuable input. If you have any questions about the EAP or how roles will be used to manage permissions in Confluence, please comment below.

Marie Casabonne

Senior Product Manager, Confluence

[Cosmo Denger]

I think we like where this is headed but have one big question.  For our clients that only access a knowledge base if we set them as "viewer" will they be able to log directly into our confluence KB without needing a Confluence license assigned?

We would like to solve for this.  https://jira.atlassian.com/browse/JSDCLOUD-14840

[Marie Casabonne]

Hey @Cosmo Denger. The interaction between Confluence and JSM is unchanged with the introduction of roles - unlicensed users will still be able to engage with Confluence and KB linked spaces as they do today. 

[Shahriman Mohammad]

Hi When this can be test , we did submit for the EAP but there is no response.

Thanks

[Rita Nygren]

I assume this means we *won't* have the option to continue to use the granular permissions after this?

[Will Stampley]

That's correct. The current plan is that eventually Confluence will go to only managing space permissions via roles. There will be support for custom roles, defined at the site level, to help cover use cases that today are covered by varied granular permission configurations.

[Tere Pile]

Looks interesting, if I can just get through migrations will see if EAP is still available! :) 

[Kate]

I would be unable to participate in the EAP, but if I could make a request for something that could potentially be added to these new permissions?

If it would be possible to have the ability to 'create or modify Automations' as a function that can be turned off/on? My org only allows selected trained users to create automations in Jira and being able to control this in Confluence as well would be extremely helpful.