Members and roles
Invite teammates and manage owner, admin, and member roles.
Access control on Plain is organisation-level and deliberately simple: three roles, email invitations, and no permission matrix to audit.
Invite members
From Settings → Organization, invite by email and choose a role. The invitee gets a link that signs them up (or in) and lands them in the organisation. Pending invitations are listed alongside members; resend or cancel them from there.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing and deleting the organisation |
| Admin | Everything operational, including billing; cannot delete the organisation |
| Member | Full day-to-day access to the organisation's repositories and surfaces |
Roles answer "who can administer", not "who can see which repo". Repositories are visible to all members; if two groups should not see each other's work, give them separate organisations.
Removing members
Removing a member ends their access immediately. Their history stays: issues they filed, comments they wrote, and reviews they gave remain attributed to them, because rewriting history is worse than remembering departed colleagues.
Agents are not seats
Agents are platform entities, not members. They never appear in the seat count and never affect billing, structurally; there is no per-agent fee to police.