Simplified permissions with role-based access controls

Managing access in Confluence has always meant wrestling with 14 individual permission checkboxes every time you add someone to a space. Over time, configurations drift, access sprawls, and admins end up granting more than intended just to keep work moving. Role-based access controls fix this by replacing those 14 checkboxes with a single role assignment — two clicks instead of fourteen.

How it works

• Four default roles ship with every site — covering the vast majority of access patterns with no configuration needed.

• Custom roles let admins define up to 10 additional roles with exactly the permissions their org requires (e.g., "Editor" who can edit but not create, or "Content manager" who can manage content but not people).

• One unified Users table shows every user, group, app, and user class with access to a space — and instantly surfaces if someone still has access through other sources when you try to remove them.

• Roles Central in Confluence admin gives you a one-stop hub to plan your transition, track progress across spaces, and bulk-convert existing permissions with intelligent role recommendations.

When roles roll out to your site, no one's existing access changes. Everyone's permissions are preserved as "Custom access" until you're ready to transition.

Availability

Role-based access controls are available to all customers on Confluence Cloud Standard, Premium, and Enterprise plans.

To learn more, read the blog post and support resources.