Managing members
Invite people to your organisation by email, manage pending invitations, and understand how accepting an invite works for new and existing Spec0 users.
Members are the people in your organisation. This page covers inviting them, what happens when they accept, and how to manage invitations that are still outstanding. Managing members requires the organisation:manage permission — Org Admin or Org Owner. See Access control.
Inviting a member
From Settings → Members → Invite, enter the person's email (and optionally the team to place them in). Spec0 sends them a branded email with an accept link.
The invite works the same whether or not the person already has a Spec0 account:
- New to Spec0. They sign up from the link and land directly in your organisation (and the team, if you set one).
- Already has a Spec0 account — even one where they're an admin of their own org. Accepting adds your organisation to the ones they belong to. They keep their existing org and can switch between them.
An invitation is tied to the email address it was sent to. Accepting requires being signed in as that address — a link can't be redeemed by someone else.
Managing pending invitations
Outstanding invites are listed under Settings → Members → Pending Invites, each with two actions:
- Resend — sends the invitation email again and refreshes its expiry. Use this if it expired or got lost.
- Cancel — withdraws the invitation and frees that email address up to be invited again. Use this if you sent it to the wrong address, or one already exists for that email and you want to start over.
The same person can hold pending invitations to different organisations at once; what's blocked is a second pending invite to the same org for an email that already has one — cancel or resend the existing one instead.
Removing a member
Removing a member from Settings → Members revokes their access to that organisation immediately — their next request fails access control. It does not touch any other organisation they belong to.
Non-human members
Don't invite a synthetic user for CI runners, CLI bots, or AI agents. Issue an API key or service-account token scoped to a team instead — it carries the same team membership a person would have, and it's bound to the organisation it was issued in. See the service-account token recipe.
Where to go next
- Organisations — belonging to several orgs and switching between them.
- Teams — placing members on the teams that own APIs.
- Access control — the roles that gate who can invite and remove.