A workspace can have more than one person. Roles are enforced on the server, not hidden in the interface: a viewer is refused by the API, not by a greyed-out button that a determined person can bypass.
The three roles
| Role | Can | Cannot |
|---|---|---|
| Owner | Everything: builds, publishing, members, domains, and the settings that affect the account. | Nothing is withheld from the owner. |
| Editor | Start builds, approve plans, publish on projects shared with them. | Manage members or the account itself. |
| Viewer | Read projects, builds, logs and artifacts. | Every write. The refusal comes from the server, so it holds even if the client is modified. |
Inviting someone
An invitation is a link tied to a role. Opening it adds that person to the workspace with the role the link was created for, and the link can be revoked before it is used. Invitations are single-purpose: revoking one does not remove a member who already accepted.
Removing a member
Removal takes effect immediately and includes projects they had been invited to. There is no grace period, because a role that keeps working after removal is not a removal. The action asks for confirmation first, since it is the one team action that cannot be waved through.
What a role does not change
Roles control access to a workspace. They do not change what the builder is allowed to do, and they do not skip the gate. A paid seat buys room, not shortcuts; the same rule applies to an editor.
Seats and plans
The pricing page describes what each plan includes. A seat is one sign-in on one workspace. If you are deciding whether you need a second one, the question is almost always “does someone else need to approve plans”, not “does someone else need to watch”.
What an editor can approve is described in How a build works, and what a viewer can never do is in Permissions.

