Skip to content
Spinbox is experimental: APIs change and data may be lost. Status lists what is built and what proves it.

Users and teams

View Markdown

A user signs in to the dashboard with:

  • GitHub, or
  • any OIDC provider: your company’s identity provider, Google, Microsoft Entra ID, Okta and others that speak OpenID Connect.

Providers are configured in Admin → Security. A provider can be the installation’s, or a team’s own. Spinbox has no multi-factor authentication of its own: require it in your provider.

The first administrator signs in with a password, from the one-time password the install wrote. Once a provider works, password sign-in can be turned off.

The CLI signs in through the dashboard, with a code the user approves (see The CLI). Sessions last seven days by default.

ModeWho can create an account
closedNobody
whitelistThe addresses and domains listed. The default, with nobody on the list.
openAnyone who can sign in with a provider

An instance administrator sees the Admin section of the dashboard and the spin admin commands. An administrator makes another user one, or disables a user, in Admin → Users.

A team holds what its members’ workspaces share: secrets, network policies, identity providers. A workspace created with --team is in the team for as long as its owner is a member. Being in a team lets nobody else in: only a workspace’s owner logs in to it, and the guests the owner adds.

RoleCan
OwnerEverything, including deleting the team. One per team.
AdminManage members and the team’s settings
MemberHave workspaces in the team
Terminal window
spin team create platform --description "Platform team"
spin team create api --parent platform
spin team member add <team-id> ana@example.com --role member
spin team member list <team-id>

Teams can be nested under a parent team. A person must have signed in once before they can be added: there are no invitations.

Membership is checked every time something is done, not only when a workspace was created. A member removed from a team loses its workspaces at once, including terminals and port connections they had open.

Users create API keys for scripts and agents, with scopes and an expiry of at most a year. A key can never approve a login or administer the installation, and makes keys of its own only with the keys:delegate scope, each holding no more than it does. See Agents and automation. Administrators see and revoke every user’s keys in Admin → Users.

Admin → Audit lists who did what: sign-ins and failed sign-ins, sessions revoked, workspaces created, started, stopped, recovered and deleted, changes to teams, to settings and to users, and runners registered. Nothing in the API can change or delete an entry.

Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.