In Confluence Cloud instances with Atlassian roles enabled, Scroll Documents uses these roles to determine what specific actions users can perform in the app.
In this article, you’ll learn about which default role can do what in Scroll Documents.
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
The next section outlines the specific actions each default role can perform in Scroll Documents.
If you want to create custom roles or provide custom access, you can find a detailed table of the minimum permissions required for specific actions in Scroll Documents in the following article: Minimum Permissions for Custom Roles and Access
What Can Each Default Role Do in Scroll Documents?
See the tables below to learn which actions each default Confluence role can perform:
Manage documents
This includes creating documents, editing document details, and deleting them.
|
Scroll Documents action |
Viewer |
Collaborator |
Manager |
Admin |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Manage versions
This includes saving versions, editing version details, and deleting them.
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).
|
Scroll Documents action |
Viewer |
Collaborator |
Manager |
Admin |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Publish and manage content
This includes publishing content to Confluence spaces and utilizing the Content Manager.
To publish to a target space, the user needs to have at least the Collaborator role in both the source and target spaces.
|
Scroll Documents action |
Viewer |
Collaborator |
Manager |
Admin |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
You require view and edit access to a page in the specific page tree in order to update properties like labels. |
|
|
|
|
Manage variants, languages, and translations
This includes adding, editing, and deleting document variants and languages, as well as managing 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.
|
Scroll Documents action |
Viewer |
Collaborator |
Manager |
Admin |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
Manage workflows and health checks
This includes managing workflows for individual documents, updating page workflow status, and running health checks.
|
Scroll Documents action |
Viewer |
Collaborator |
Manager |
Admin |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|