Members, teams & roles

An organization can have a whole crew. Invite teammates, give each the access they need — from read-only to full owner — and manage them from the CLI or the portal. Roles keep the money and the destructive buttons in the right hands.

Invite a teammate

bootload org invite teammate@example.com --role developer

They get an email with a link; once they accept (signing up or logging in), they join the organization with the role you chose. Invites expire after 7 days — re-invite if one lapses. --role defaults to viewer if you leave it off.

Roles

Role	Can do
`owner`	Everything, including managing owners and deleting the organization
`admin`	Manage members and all resources — but can't grant the owner role
`developer`	Deploy and manage services, volumes, domains — the day-to-day workload
`billing`	Manage the wallet, top-ups, payment details and spend caps
`viewer`	Read-only — see everything, change nothing

Two guard rails keep ownership safe:

Only an owner can grant the owner role — an admin can't mint a peer who could then remove them.
The last owner can't be demoted or removed — an organization always keeps at least one captain.

Manage the crew

bootload org members                                  # who's aboard, and their roles
bootload org member set-role teammate@example.com admin
bootload org member remove teammate@example.com

Only owners and admins can invite, change roles, or remove members. The portal has the same view on the members page.

A note on the account vs the organization

Each person has their own account (their login, profile, and 2FA). An organization is the shared workspace they're a member of — its projects, wallet, and services. Removing someone from an organization doesn't touch their account; it just revokes their access to that workspace.