Atlassian is slowly rolling out roles to Confluence, replacing the original space permissions.
In this article, you’ll learn the minimum permissions required to perform specific Scroll Documents actions using custom roles or custom access.
Please note
Since roles is a new beta feature in Confluence, the roles and permissions needed for certain actions may change as the feature is updated. If you notice somethings has changed since last time we updated this article, don't hesitate to contact our support.
Last updated:
Difference Between Default Roles, Custom Roles, and Custom Access
Confluence provides the following default roles to manage actions at the space level:
-
Viewer
-
Collaborator
-
Manager
-
Admin
Each default role includes a predefined set of role permissions with actions that users can perform within the space which you can find documented.
You can assign a user or group one of these default roles or provide custom access by manually selecting specific permissions outside of the presets. You can also create custom roles to use as templates, if you want to reuse the same combination of permissions several times.
You can manage role permissions for a space within the Users section of your Space settings, or under Security within the Confluence administration screen. For more information on roles, refer to the Confluence documentation: Manage user roles
Proceed to the next section to learn the minimum role permissions required for specific Scroll Document actions.
If you prefer using default roles, the following article provides a detailed table of the actions each role can perform in Scroll Documents: Assign the Required Roles
Which Role Permissions Are Required for Specific Scroll Documents Actions?
If you want to set up a custom role or give a user custom access to a space, you can see what role permission they need below for what actions:
|
Scroll Documents action |
Minimum role permissions needed |
|---|---|
|
Create a document |
|
|
Edit document details |
|
|
Delete a document |
|
|
Move a document |
|
|
Save a version |
Before saving a version, ensure the user has view and edit access to all pages that the new version is based on (usually the Working version). |
|
Edit version details |
|
|
Delete a version |
|
|
Copy a version |
|
|
Use Organize page tree |
|
|
Use Add existing page tree |
|
|
Publish to Confluence |
The following role permissions are required in both the source and target space. |
|
View activity |
View content |
|
Compare versions |
View content |
|
Overwrite |
|
|
Manage restrictions |
|
|
Use Content Manager |
You also require access to the pages in that specific page tree. If you are is restricted from viewing or editing a specific page, you will not be able to update properties like labels. |
|
Manage variants |
|
|
Manage languages and translations |
Before adding or updating a translation, ensure you have view and edit access to all pages in the authoring language. If you are updating an existing translation, you will also need these permissions for the translated page tree. |
|
Enable, switch, and disable workflows |
|
|
Change workflow status |
|
|
Perform health checks |
View content |