Brightspot CMS User Guide

Limiting a role's access to workflow transitions


You can limit a role’s access to certain workflow transitions. For example, you may want one role to do only content editing, and another role to do only proofreading.

Note
Limiting a role's access affects all users who have the role.

To limit a role’s access to workflow transitions:

  1. Click menu > Admin > Users & Roles.
  2. In the Roles widget, select the role whose available transitions you want to limit.
  3. Under Permission Settings, under Types, select All Except.

    Workflow edit tool role

  4. Under Restricted Types, select Content Type.

    Workflow restricted types
    Restrictions on content type-transitions for a role

  5. From the Type list, select a content type.
  6. From the Actions list, select All Except.
  7. From the Type Actions list, select the transitions that you want to exclude from the role.
  8. Repeat steps 4–7 to add additional restrictions for content type-workflow transition combinations.
  9. Click Save.

Referring to the illustration in Create a custom workflow and the above illustration in step 4:

  • When the role is working on an article, and
  • When the article is in status Pending Review, then
  • The role can only reject the article, not approve it.
  • All other roles can both approve and reject the article.

Workflow reject
Workflow options for role with limited permissions

Workflow reject accept
Workflow options for role with unlimited permissions
Previous Topic
Modifying a workflow
Next Topic
Conversation administration
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Modules
Landing pages
Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

Dashboards
Publishing
Workflows
Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform, including integrations requiring developer support to use.

Field types
Content modeling
Rich-text elements
Images