A permission matrix of four resources against the Admin, Editor and Reviewer columns, the levels running publish to none in weakening weight, with a view-as control sitting on the tinted Editor column Viewing as Editor RESOURCE ADMIN EDITOR REVIEWER Pages Entries Media Components Publish Publish Publish Publish Edit Edit Edit Read Read Read Read None

Your stack. Your rules. Everyone moves faster.

What roles and permissions do

  • Five ranked roles

    Admin, developer, marketer, editor and reviewer. Each role carries a one line description of the job.

  • View as another role

    Look at the CMS from a role below your own. Every gate reads it, so the preview tells the truth.

  • Custom roles

    Seven capabilities, grouped by the job they belong to. A custom role narrows a built in role. It never widens one.

  • A permission matrix

    Eight resources at four levels, in one table. Custom roles appear as computed columns.

  • Page and agent locks

    Lock a page and everyone stops editing it. A second lock holds the agent off on its own.

Role questions.

What teams ask before they hand the CMS to more people.

  • A built in role is one of the five ranked levels. A custom role narrows a built in role to a smaller set of sections or actions. It never widens one.

  • Yes. The role belongs to the workspace, not to the person, so one account can be an admin in one workspace and a reviewer in another.

  • Yes. View-as switches you into any role below your own, and every gate in the app reads the effective role, so what you see is what they get.

  • Publishing is one of the things a role decides. A reviewer can comment, an editor can change content, and publishing sits above both.

See the CMS from every role

Content OS for modern websites.