Team roles

Owner, admin, editor, viewer. Send an invite and the role decides the rest.

Step-by-step documentation Manage workspaces, invitations, roles, and access

Sites get built by more than one person: a designer who should be able to change anything, a copywriter who should be able to change the words, a client who should be able to look and not touch.

Invite people to the workspace by email address, give each of them a role, and the role decides the rest — across every site in the workspace, in the dashboard and in the editor alike.

The roles

  • Owner — everything, including billing and deleting the workspace. There is one.
  • Admin — everything except the things only an owner should do. Can invite people and manage sites.
  • Editor — opens the editor, changes pages, publishes. Cannot touch billing or remove a site.
  • Viewer — can see the work and say what they think. Nothing they click will change anything, which is the point of handing this one to a client.

The restriction is real, not cosmetic: what a role cannot do is not rendered as a disabled button for them to argue with, and it is enforced on the server rather than in the page.

How to do it

  1. Open Members in the workspace.
  2. Invite by email address and pick the role.
  3. They accept and land in the same workspace, on their own account.
  4. Change or remove a role whenever the project changes.

What it costs

Team members are on the paid plans; how many depends on the plan. See the pricing page.