Documentation · Administration
Members and roles
The four roles and what each may do, inviting people, handing the organisation over, and closing it.
Everyone in an organisation has one of four roles. The people and their roles are under Settings → People, and nobody is charged per seat.
| role | what it is for |
|---|---|
| Owner | Full control, including handing the organisation to somebody else. |
| Admin | Everything except transferring ownership and closing the organisation. |
| Member | Can see runs, workspaces and history, but cannot change them. |
| Billing | Invoices and payment only — no access to runs or workspaces. |
The organisation's first owner is the person whose sign-up created it. An organisation can have more than one owner.
| action | Owner | Admin | Member | Billing |
|---|---|---|---|---|
| Cancel a CI job, or apply, discard or cancel a Terraform run | yes | yes | — | — |
| Open a migration pull request | yes | yes | — | — |
| Connect GitHub or the Terraform engine | yes | yes | — | — |
| Change organisation settings: the concurrency limit, protected sticky disks, resetting a disk, requiring two-factor | yes | yes | — | — |
| Invite people, change their roles, remove them | yes | yes | — | — |
| Add a card, change billing details, ask for sticky disks or a static IP, set spending alerts and the spending cap | yes | yes | — | yes |
| Download the usage CSV | yes | yes | — | yes |
| Hand the organisation to somebody else | yes | — | — | — |
An admin cannot change or remove an owner, or make anybody an owner. Closing the organisation is for owners too; see below.
Under Settings → People, an owner or an admin enters an email address and a role, and presses Send invitation. The role can be Member, Admin or Billing, but not Owner: an owner can make somebody an owner once they have joined.
The invitation is emailed, and the page also shows its link, so you can send it yourself if the email does not arrive. It lasts seven days and works only for the address it was sent to, so the person signs in or signs up with that address to accept it. Pending invitations are listed with their expiry, and Revoke cancels one.
If you have two-factor authentication on, sending or revoking an invitation asks for a code when you last gave one more than fifteen minutes before.
An owner or an admin changes somebody's role with the role menu on their row under People, and Remove takes them out of the organisation. An owner can make another member an owner the same way. Leave on your own row takes you out; the only owner cannot leave until somebody else is an owner.
An owner can also hand the organisation over: Make owner on another member's row, then Hand over. The new owner has everything, and the one who handed it over becomes an admin.
On Settings, under Closing things down, an owner can close the organisation by typing its slug to confirm and pressing Close this organisation. No new CI job or Terraform run starts after that.
Nothing is deleted. Your history, your invoices and your Terraform state are kept, and everyone keeps their sign-in. Closing cannot be undone from the dashboard.