Roles and permissions

Everyone in your Organization has one of four roles: Reviewer, Editor, Admin, or Owner. The roles stack. Each one can do everything the role below it can, plus more, so an Admin is also an Editor and a Reviewer.

A person's role is set for the whole Organization and applies in every Project and Workspace in it. There are no separate per-Project or per-Workspace roles today.

The four roles

• Reviewer can open the Organization's Workspaces, look at the running app, and leave comments, but can't make changes. It's the right role for stakeholders who give feedback.
• Editor can do the actual work: start Workspaces, edit with the Style Editor, Soffi, and the code, and Ship pull requests. Editors can also invite people as Editors or Reviewers. People who join through an approved access request, or automatically through your company's email domain, start as Editors.
• Admin sets things up: creates and configures Projects, publishes them, connects GitHub and other integrations, and manages members.
• Owner is the one person accountable for the Organization. There's exactly one, and the role moves only by transferring ownership.

What each role can do

Organization

Project

Workspace

Limits worth knowing

You can only grant up to your own tier. Editors can invite and re-role people as Editors or Reviewers, and can't change an Admin's role. Admins can grant Admin and below. Nobody can make someone Owner by invitation or role change; the Owner transfers ownership instead, from the Organization's settings.

Some Organizations limit invitations to the Owner. When that setting is on, only the Owner sees Members in Settings and can send invitations.

Reviewers can ask for more. A Reviewer who opens a Workspace can choose Request edit access. An Admin, or an Editor, can approve it, and the Reviewer becomes an Editor.

To add people and set their roles, see Invite your team.