Who gets into your workspaces
A workspace lets in you, its owner, and the guests you let in, each with a key that logs in as
them. A key logs in as you only once you add it with your passkey: somebody with your session,
an agent or an API key cannot add one, and so gets no shell in your workspace and lets nobody in.
The one API key that runs commands in your workspaces is one you made with your passkey and the
workspace:exec scope, for a program to use (spin.v1.ExecService); every call it makes is in
the audit log. Give it keys:delegate and it makes keys of its own for the agents it starts
(spin mcp serves them the API): each holds no more than it does - its scopes, team, projects,
end, and how many workspaces and cores all of them hold - and goes when you revoke it. Why, and
what it trades, is
ADR-0031.
The control plane decides who logs in, at every session: it certifies a key of yours, for five
minutes, into a workspace you own or are a guest of. It also holds what it needs to serve you: your
token on a forge, within what its app may do, and your team’s secrets. docs/security/README.md
says what this does not protect. Protect a repository’s branches on the forge, and keep a team’s
secrets as references, which your cloud’s own log records the reading of.
Your passkey
Section titled “Your passkey”You sign in with GitHub (or your installation’s provider). Your passkey is what turns that session into something that logs in: your first one is registered from the dashboard, and your password manager brings it to your other browsers, where it works as it is. Past the first, a passkey is added with one you already have.
A passkey your password manager syncs is as safe as that manager’s account: whoever gets into it asserts as you. A security key stays on the device.
If you lose every passkey, ask an administrator to clear them, and register a new one from your sign-in. Nothing you made is lost: your keys and workspaces are your account’s.
Your keys
Section titled “Your keys”- A key of your own - an SSH key on a laptop, a FIDO2 key - is added once with your passkey and
stays until you delete it. From a terminal,
spin ssh-key add <name> <key.pub>opens the page where your passkey confirms it, and waits. - This browser’s key. The browser’s terminal and editor make a key of their own, one no script can read out, and your passkey adds it for twelve hours. Until then they ask you nothing.
spin ssh-key list shows both, with when a browser’s runs out. A key you delete logs in nowhere
from the next session; one already open goes on until it ends.
What you set, and what a workspace applies
Section titled “What you set, and what a workspace applies”Your settings - your dotfiles and the command that installs them, your login shell, environment,
editor settings and Taskfile, and a workspace’s own environment (--env) - are what a workspace
applies. Each workspace is given only what is its own: another workspace’s environment never
reaches it, and a workspace with a guest in it, or cloned from somebody else’s snapshot, is given
none of your dotfiles, environment or Taskfile. Letting a guest into a workspace that already
applied them takes your environment file and your Taskfile’s tasks out; dotfiles already installed
stay installed, since nothing uninstalls them - so take out anything secret from a workspace before
you let somebody in. A commit is checked out only in the history of the ref the workspace opens.
What leaves a workspace - its journal, its console, the agent’s thread index - is the installation’s policy, not yours, and so is the egress root a workspace trusts and who its identity is given for. A clone of a snapshot is given an identity as any workspace is: its disk runs what whoever made it put there.
Sharing a workspace
Section titled “Sharing a workspace”spin workspace guests add <workspace> <email> (or the workspace’s Access tab) lets a person in,
confirmed with your passkey. They log in with a key of their own, as you do.
A guest can connect, see the workspace and open its ports as private. A guest cannot change who logs in, or the workspace itself through spin: no start, stop, snapshot or delete. Inside the machine, a guest is root, as you are: share a workspace with somebody you trust with it.
spin workspace guests remove takes a guest out: their next session is refused, and one already
open goes on until it ends.
Generated by task reference from spin/docs/access.md at 51f7e0dea.
Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.

