Members, roles and teams
Who belongs to the organisation, with which role, and in which teams. An owner invites, changes a role, removes a member and builds the teams; everyone else sees the list.
The organisation's three roles
| Role | What it allows | Includes |
|---|---|---|
| owner | Everything: settings, models and their keys, members and teams, cost. Saves agents, revokes a remote agent. | approver |
| approver | Decides gates, starts and resumes runs, proposes actions from Work that another member signs, requests a remote agent's arrival. | viewer |
| viewer | Reads runs, proof and the Mesh, asks questions in Work. Decides, starts and proposes nothing. | — |
Inviting
- An owner invites by e-mail, with the role to grant.
- The invitation goes out by e-mail, valid 7 days; the person accepts it from the link and joins the organisation with that role.
- Pending invitations are listed with their expiry; an owner can cancel one. There is no resend: cancel, then invite again.
Changing a role, removing a member
An owner changes a member's role or removes them from the organisation. The last owner can be neither demoted nor removed: an organisation always has someone to run it. Removing a member takes their access away; their account is not deleted.
Teams
A team groups members around a scope. An owner creates teams and adds or removes members, each with a team role: lead, approver, member or viewer.
- An agent belongs to a team: the Mesh's team filter, team policies and reserved collections apply to it.
- A team's approver or lead decides whether a remote agent joins it.
- A two-signature rule can require signers from different teams, or a signer from a named team.
Not yet
SoonInviting straight into a team: today, the person first joins the organisation, then an owner adds them to the team.