Scroll Roles classify users into three roles, which space admins can assign from Scroll Add-ons > Administration > Scroll Roles. These are especially useful in larger teams, where responsibilities might be distributed across multiple people. Real-life responsibilities can be mapped to these roles.For example, if you have external writers working on your content, they can be assigned as Authors, while your internal tech writers who are responsible for the overall documentation, can be assigned as Doc-Admins.
In the majority of cases, using Confluence Permissions is a simpler and more intuitive approach to granting permissions. Scroll Roles should be used if the required permissions cannot be assigned otherwise. For example:
The permissions in spaces managed with Scroll Versions depend on the permissions set for the space and if specific users and groups are assigned to the Scroll Versions roles.
- If Authors and Reviewers are explicitly defined in a space, Doc-Admins have to be explicitly defined as well. Otherwise, Doc-Admins won't be able to see or create versioned pages.
- Group and user pickers in Roles configuration or Page Restrictions screens do not consider if a certain group or a user has access to the space. Please review which group and users have access on the Space Permissions screen before adding roles and restricting versions or pages.
An administrator for Scroll App modules. Doc-Admins can act as author, reviewer, and reader. They can execute Health Checks, edit version permissions, convert pages to Unversioned, reschedule pages, and delete page versions.
|Reviewer||A Reviewer can browse through versions, compare page versions and access Scroll Versions-related page metadata, and review content that has been submitted for review in a Workflow.||If Scroll Versions is activated|
|Author||An Author can create and edit pages in versions, convert pages to Versioned. They can submit drafts for review in a Workflow. If reviewers are not explicitly defined, Authors also act as Reviewers.||If Scroll Versions is activated|
|Reader||A Reader can view unversioned pages or (published) master pages. Readers aren't explicitly defined. Users with Confluence view permissions and without any Scroll Roles assignment are considered to be readers.|
Scroll Versions has a built-in workflows that track the state of each page and provides functionality for approvals.
A user can perform different transitions depending on their role:
|From Draft, to Review||From Review, to Draft||From Review, to Complete||From Complete, to Draft|