Summary:
Customers require more granular role-based access control (RBAC) in Confluence, specifically the ability to assign Automation and Analytics permissions separately from the all-powerful “Manage everything in this space” (Space Admin) permission. This will enable organizations to delegate responsibilities more securely and flexibly.

Use Case

Background:
Currently, Confluence’s RBAC model groups several powerful permissions—including content management, automation, and analytics—under the broad “Manage everything in this space” (Space Admin) role. This limits organizations’ ability to delegate specific responsibilities without granting full administrative access.

Requested Enhancement:

• Split Automation and Analytics permissions from the “Manage everything in this space” permission.

• Allow these permissions to be assigned independently to custom groups or roles within a Confluence space.

• Ensure that this granularity is available in both the UI and via APIs for automation.

Example Scenario:

• A team wants to grant a user the ability to manage automation rules (e.g., page creation triggers) without giving them access to all space admin functions.

• Another user should be able to view and manage analytics for a space, but not modify content or automation settings.

Business Impact

• Security: Reduces risk by following the principle of least privilege.

• Operational Efficiency: Enables organizations to delegate tasks without over-provisioning access.

• Compliance: Supports organizations with strict access control requirements.