Workspaces
Personal and team workspaces, switching between them, member roles.
A workspace is the unit of pooled session memory in Spooling Cloud. Every developer has at least one (a personal workspace, created for them on first sign-in). Teams add team workspaces for shared memory across people.
Personal vs team
| Personal | Team | |
|---|---|---|
| Created by | Auto on sign-in | You, from the workspace switcher in the app |
| Members | Just you | Multiple, with roles |
| Pricing | Free | Free today. Paid Team and Business plans are planned (see pricing) |
| Shared search | n/a | Across every member's pushed sessions |
| API keys | Yours only | Per-member keys; each key is scoped to one workspace |
Switching the active workspace
The admin GUI shows a workspace switcher in the top-left sidebar. Picking a different workspace updates a cookie (spooling-ws) and re-renders the rest of the page scoped to that workspace.
The CLI is workspace-bound by API key, not by the cookie. Every key reads and writes exactly one workspace. To switch where the CLI pushes, sign in again and choose the other workspace when the browser asks:
spooling loginspooling cloud login reference →
Member roles
Each member of a team workspace has one of three roles:
- Owner: manages members, invites and roles, and can make other owners
- Admin: manages members and invites, but can't make someone an owner
- Member: can search and push, and manage their own API keys
A team always keeps at least one owner. Roles are managed on the Members page in the app.
API keys are per-workspace
This is the most important thing to internalize about workspaces. A key minted in Workspace A cannot read or write to Workspace B, even if you're a member of both. The cloud's auth path resolves the key → workspace at request time and refuses any cross-workspace operation.
Practical implication: to push to a team workspace, run spooling login and choose that team on the approval page (or mint a key for it in the app and use spooling cloud login --key …).
Cross-workspace flows
If sessions are already in the wrong workspace, or you want the same session in both, see Working across multiple workspaces.