All posts

Tutorial

Roles for editors, publishers and admins

Three roles, one clear rule: who may change what visitors see. A guide to editor, publisher and admin in ATLAS.

Every member of a brand has one of three roles. The line between them follows one question: does this action change what visitors see?

Editor

Writes and edits drafts, uploads media and asks for a review. An editor can also create a short lived preview token to show a draft to someone. Nothing an editor does reaches the live site on its own.

Publisher

Everything an editor can do, plus anything that changes live output: publish, schedule, roll back, unpublish, approve reviews and move published pages. Publishers also handle form submissions and leads.

Admin

Everything a publisher can do, plus the brand itself: settings, members, API tokens, integrations and secrets, and imports. Secrets are write only: once saved, even an admin cannot read them back.

Built in, not bolted on

  • Every live change writes an audit row: who, what and when.
  • Roles are per brand, so someone can be an admin on one brand and an editor on another.
  • A content type can require a minimum role, for example only publishers may touch the pricing pages.

//Keep reading

More from the blog

All posts →

//Run every brand from one place.

Start with one brand for free. Bring your team when you are ready.

$ npm install @atlas/client @atlas/nuxt

Free for one brandNo credit cardUpgrade anytime