We are around 1k+ users and wanted to move to Role-Based Access Control (RBAC) from individual user Access in Confluence.
As a admin any steps how we can do this
Hi Mani, good question — and a very common one at your scale. Confluence Cloud doesn't have a built-in "role" object the way some other systems do, so in practice RBAC is done with groups, and the groups then act as your roles. A practical way to go about it: 1. Define the roles first — for example Viewer, Editor and Space Admin — and agree what each one can do in a space (view pages, add and edit pages, manage permissions). 2. Create one group per role in Atlassian Administration and put your users into those groups. This is also where you control who has product access to Confluence at all, which is separate from what they can do inside a space. 3. In each space, go to Space settings > Permissions and grant permissions to the groups rather than to individual users. Start with one pilot space and check the result before rolling it out more widely. 4. Set the default space permissions so new spaces start from the same role groups instead of individual names. 5. Once a space is working on groups, remove the old individual grants a few at a time, and keep the audit log in Atlassian Administration handy so you can spot anything that breaks. 6. Keep guests and external users in their own group, so they never accidentally pick up internal permissions. The habit to keep afterwards is to make access changes by adding or removing someone from a group, never by editing a space directly — that is what stops the individual grants creeping back. If you are on Data Center rather than Cloud, the same group-based approach applies, just managed in the Confluence admin area instead. Hope that gives you a workable starting point — happy to expand on any of the steps.
Hi Mani,
Good timing 😅, because Confluence Cloud now has roles built in. There are four default roles (Admin, Manager, Collaborator, Viewer), and Confluence admins can create up to 10 custom roles. roles can be assigned to users, groups and user classes such as All Confluence users.
for 1,000+ users, this is roughly the order Atlassian recommends.
could you check whether your spaces already show a Role column under Space settings, Users? That tells you whether roles have reached your site yet.
Adding one angle that often gets overlooked in a move like this: page-level restrictions.
Space permissions and roles don't rewrite page restrictions. If individual users were added directly to specific pages over the years, those entries stay in place after you move space access to roles or groups, which can lock people out or keep access wider than you intended.
Two habits that help before and during the migration:
Spot restricted pages early. There is no single built-in report that lists every restricted page in a space, so check the lock icon on your key page trees, and use Inspect permissions where your plan has it, to see who currently has view or edit access.
Swap before you strip. Add the new group on the affected pages first, then remove the individual names, so nobody hits a dead end mid-cutover. Keep in mind that view restrictions carry down to child pages, while edit restrictions are set page by page.
Disclosure: I work at Atesen Software, and we build Bulk Page Restrictions for Confluence, which previews and applies restriction changes across a page tree: https://marketplace.atlassian.com/apps/350305877/bulk-page-restrictions-for-confluence . You can also do this by hand, page by page, without any app.
I think you are looking for this article :-) It has all the details:
https://community.atlassian.com/forums/discussion/3268240/confluence-rbac-rollout-check-your-fallback-role-before-the-transition-window-closes
Hi @Mani Chaitanya ,
One small addition: space admins can find restricted pages under Space settings → Content → Restricted in Confluence Cloud. That’s a useful starting point for reviewing page restrictions before moving to group-based access.
Atlassian documents this under “Find restricted content in a space”.
It looks like you're new here. Sign in or register to get started.