Team and accountTeams and roles
Teams and roles
A team owns projects, domains, integrations and the plan. Create one, invite people as owners, admins, members or viewers, see who is active, and remove people or leave. Owners can delete the team.
What a team is
Everything on Orbits belongs to a team: its projects and their deployments, domains and Orbits DNS zones, integrations, API tokens, alerts and the plan. You can belong to several teams; the team switcher at the top of the web app moves between them. Each team has its own members, roles and security rules.
Create a team
You create your first team when you sign up. To make another, open the team switcher and choose Create a team. You need:
- Team name: what people see.
- Team URL (the slug): the team's address in the web app,
orbits.africa/<slug>. 3 to 40 characters: lowercase letters, digits and dashes, starting and ending with a letter or digit. It must be unique across Orbits, and a few words the web app uses for its own pages, such asapi,admin,settings,loginanddocs, are reserved.
You can invite up to 20 teammates in the same step. You become the team's owner.
To change the name or URL later, go to Team › Settings › General. Old links to your dashboard stop working if you change the URL. The team's id (team_…) never changes, and the API accepts either.
The Default region is Abuja (abj-1), the only region.
Team avatar
On Settings › General, upload a square image (at least 256 px works best) and crop it. PNG, JPEG or WebP; the source can be up to 10 MB, and the cropped avatar is at most 150 KB. Owners and admins can change it.
Roles
Every member has one role in the team.
| Role | In short |
|---|---|
| Owner | Everything, including billing, members and deleting the team |
| Admin | Everything an owner can, except billing, deleting the team and handling other owners and admins |
| Member | Create projects, deploy, manage domains, variables, flags and alerts |
| Viewer | See projects, deployments and logs. Can't change anything |
What each role can do
| Owner | Admin | Member | Viewer | |
|---|---|---|---|---|
| See projects, deployments, logs, observability, analytics, activity | Yes | Yes | Yes | Yes |
| Create projects | Yes | Yes | Yes | No |
| Deploy, redeploy, cancel, promote, roll back | Yes | Yes | Yes | No |
| Add, change, reveal and pull environment variables | Yes | Yes | Yes | Keys only |
| Add, change and remove domains and DNS records | Yes | Yes | Yes | No |
| Create and change alerts, flags; run workflows; switch Analytics and Speed Insights | Yes | Yes | Yes | No |
| Change project settings, pause, delete a project | Yes | Yes | No | No |
| Move a project to another team | Yes | Yes | No | No |
| Team settings, security rules and notification switches | Yes | Yes | No | No |
| API tokens, integrations and the alert webhook | Yes | Yes | No | No |
| Invite people and manage invites | Yes | Yes | If allowed | No |
| Change roles and remove people | Yes | Members and viewers | No | No |
| Make someone an owner or admin | Yes | No | No | No |
| Pay for Pro, cancel or resume it, see invoices | Yes | No | No | No |
| Delete the team | Yes | No | No | No |
| Get the team's emails (failed deploys, alerts, domain problems) | Yes | Yes | Yes | No |
Moving a project to another team also needs you to be an owner of the team it's going to.
A team always keeps at least one owner. Someone who isn't a member of a team gets "not found" for it, never "forbidden", so a team's name isn't given away.
Invite people
On Team › Members, enter one or more email addresses (up to 20 at a time, or paste a list), then pick a role. Each person gets an email with a link to join. Invites expire after 7 days.
- Addresses that already belong to a member, or already have a pending invite, are skipped.
- Pending invites show in the member list. Resend emails a fresh link and renews the 7 days; the old link stops working. Revoke invite takes it back.
- You can also make a reusable link for a role and share it yourself. Anyone with the link can join until it expires or is revoked.
An email invite can only be accepted by someone signed in with that email address. Someone without an account signs up from the invite page first.
Who can invite
Set under Team › Settings › Security › Who can invite people:
| Setting | Who can invite |
|---|---|
| Owners only (the default) | Owners and admins |
| Owners and members | Members too, but only as a member or a viewer |
Viewers can never invite. Only an owner can invite someone as an owner or admin.
The member list
Team › Members lists active members, then pending invites. Search by name or email. Each row shows the person's role, whether they have two-factor on, and Last active:
- Active now while they have the team open.
- Otherwise, when they last used this team, to the minute.
- Never if they haven't used the team since Orbits started recording it.
Last active counts the person using the team in the web app or with their own session. Work done with an API token doesn't count: a script isn't the person.
Change a role
From the member's row menu, pick a new role. Owners and admins can move people between member and viewer; only an owner can make someone an owner or admin, or change an owner's or admin's role. The last owner can't be demoted: make someone else an owner first.
Remove someone, or leave
- Remove from a member's row: owners and admins can remove members and viewers; only an owner can remove an owner or admin.
- Leave the team from your own row. You can leave even when the team requires two-factor and you don't have it on.
The last owner can't leave or be removed. Make another member an owner first.
When someone leaves or is removed, their API tokens for the team stop working at once, and stay dead if they rejoin.
Delete a team
On Team › Settings › General, under Danger zone, press Delete team and type the team's URL to confirm. Only owners can, and it can't be undone.
What goes, in order:
- Its Git connections. GitHub's app is uninstalled from the account, and GitLab and Bitbucket webhooks are removed. If Orbits can't do this, nothing is deleted and you can try again.
- Its domains and Orbits DNS zones.
- Every project, with its deployments, environment variables and alerts. Deployed apps stop being served.
- Its activity, alert webhook and notifications.
- The team, with its members, pending invites and avatar.
If the team is on Pro, the plan ends with it, with no refund: nothing is charged again and the saved card is forgotten. Invoices already paid are kept as the record of the payment.
From the API
The team calls are under /v1/teams and /v1/teams/{team}/members and /invites. See API › Teams. API tokens can read the team, but can't manage members or invites, change security rules or delete the team.