Coordinator · Your team
Roles and access
Every person has a role in your organisation, which decides what they can do anywhere in Coordinator. Each project then decides who can see it.
Organisation roles
| Role | Can |
|---|---|
| Admin | Everything a member can, plus see every shared project in the organisation, add or remove its collaborators, and change which team it is shared with |
| Member | Create projects, and create and work on items in the projects they are given |
| Viewer | Read the projects they are given, and change nothing |
An admin is not a project's owner. An admin cannot delete someone else's project or change its settings, and cannot see a project its owner has made private.
A viewer can still manage their own account: their email settings and their personal keys. When a viewer tries to change anything else, Coordinator refuses and says their seat is read-only. An AI connected as a viewer is held to the same rule.
Who sets the role
Your organisation's admin sets each person's role in Vista, where your organisation's people are managed. A change applies on the person's next action, in the browser and through their AI alike.
When an admin deactivates someone, they are signed out, their personal keys stop working, and their next action is refused. Reactivating them restores the account; old keys stay revoked.
Project access adds to the role
A project is shared with a team, with everyone in the organisation, or kept private, and its owner can add individual collaborators as viewer, commenter or editor. See Give someone access to a project.
The organisation role always wins. A viewer added to a project as an editor can still only read it.
Updated 14 November 2026