Security and compliance

Who on my team can see and change what?

Roles decide it, and a role can be scoped down to an individual field. The built in roles are admin, developer, marketer, editor and reviewer, and custom roles narrow the permission set further. A reviewer comments and approves without edit rights. Roles change what a member can do and not what a member costs, because every Workspace member is the same $15 a month.

The five roles

Admin runs the workspace, its billing and its people. Developer works on the content model and the components. Marketer composes and publishes pages. Editor writes and edits within what exists. Reviewer reads, comments and approves.

The line worth noticing is between marketer and editor: one can put something on the internet and the other cannot.

Custom roles, down to the field

When the five do not fit, a custom role narrows the permission set, and the scope reaches individual fields. The common use is a role that may edit a page but may not touch its SEO fields or its published path, which is a genuine distinction on a site where search traffic pays the bills.

Why the reviewer has no edit rights

A reviewer who can edit stops reviewing and starts fixing, and the record of what was wrong disappears with the fix. Keeping the approver out of the document is what makes request changes mean something.

It is also why the price ignores role. Every Workspace member is $15 a month, so approval is never rationed by a budget line.

Also in security and compliance

All of security and compliance All questions

Still have a question left

Thirty minutes with the product team, and a straight answer.