Docs / How-to guides
Teams and workspaces
Switch workspaces, invite people in one of four roles, pay for their seats, and move a server between workspaces.
Every server belongs to a workspace, and so do API keys, domains, webhooks and the bill. The workspace made for you when you first sign in is yours alone. On Pro or Scale, you can invite people to it, each in one of four roles.
Switch workspaces
The switcher at the top of the sidebar shows the workspace you're in, its plan, your role there and how many people it has. Press W to open it, and type to find a workspace by name. Choosing one opens its Dashboard. The switcher also has Members and settings and Create a workspace.
From the CLI, sokie workspace use acme works in that workspace from then on, on this computer, and --workspace acme works in it for one command. The CLI reference has the details.
The workspace's address
A workspace's pages live under its address, like sokie.sh/acme/servers. The address starts from the workspace's name and follows it when you rename the workspace.
To change it, open Settings, and under Workspace, type a new one in the Address card. It takes lower case letters, digits and dashes, from 2 to 40 characters. The old address forwards to the new one until the address changes again, so update your links and the CLI soon. An address you change by hand stops following the name. Only owners and admins can change it.
Roles
| Role | What they can do | Seat on Pro |
|---|---|---|
| Owner | Billing and the plan, deleting or handing over the workspace, and all an admin can | Yes |
| Admin | Members and roles, domains, webhooks, GitHub and security settings, approving what members ask for, deleting servers, and all a member can | Yes |
| Member | Create and deploy servers, restore, edit tools and set secrets | Yes |
| Viewer | See servers, logs, usage and the audit trail, and connect their own agents to team-only servers | No, free |
A workspace has one owner. Some changes are for owners and admins only: deleting a server, opening one to more people, and removing an address callers use. A member who tries one gets Ask an admin instead (Ask an admin). A server can also hold members' deploys for an admin (Deploys that wait for an admin).
An admin can trust one member further, under Can also when they open that member:
- Can delete servers: deletes a server without asking an admin. It still takes typing the server's name, and it's in Audit.
- Deploys without approval: their deploys go straight to production on servers that hold deploys for an admin.
An API key never does more than its maker's role allows.
Invite people
In Settings, under Workspace, open Members and choose Invite people.
- Type their email addresses, separated by commas, spaces or new lines. You can invite up to 50 at once.
- Choose what they join as: admin, member or viewer.
- Choose Send invite.
Each person gets an email with a link that works for 7 days. They sign in to Sokie with the address you invited to join, and land in the workspace. If they're signed in with another address, the page asks them to sign in with the invited one.
Invites not yet answered are listed under Invites waiting, with who sent each and when it expires. Withdraw ends one, and its link stops working. Inviting the same address again replaces the earlier invite.
Owners and admins invite people and change their roles. Everyone in the workspace can see who's in it.
Seats and plans
Hobby and pay as you go are for one person. Members come with Pro and Scale.
On Pro, each owner, admin and member takes a seat, at $19 a month or $190 a year; viewers are free. A seat is charged when someone accepts, for the rest of the month or year, and nothing is charged for an invite nobody accepts. Each extra seat also adds tool calls and servers to the plan: Limits and plans has the numbers.
If a workspace moves from Pro to a plan for one person, only its owner can get in. Everyone else stays listed, suspended, for 30 days, with nothing deleted. Back on Pro before then, they're back, and their seats are charged from that day. After 30 days, they're removed.
Change a role or remove someone
On the Members page, open a person to change their role and choose Save. A role change takes effect at once.
Remove from the workspace takes them out:
- They can't open the workspace from their next click, and their CLI can't reach it.
- Their API keys and deploy keys in it are revoked, so CI that uses them stops deploying.
- Their agents lose their connections to its team-only servers.
- Their servers, deploys and secrets stay: they're the workspace's.
- On Pro, their seat is credited for the rest of the period, on the next invoice.
The owner can't be removed. To step down, the owner opens an admin and chooses Hand it over: that admin becomes the owner, and the old owner an admin.
Make another workspace
Open the switcher and choose Create a workspace. Give it a name and an address, and choose monthly or yearly billing.
Every workspace you make after your first is billed on its own and starts on Pro. The first time, it's free for 14 days: Stripe takes a card and charges nothing until the trial ends. After that, Pro starts at once. Your first workspace stays as it is, with its servers.
Move a server to another workspace
If you own two workspaces, a server's Settings tab has Move to another workspace. Choose Move server…, then the workspace to move it to.
Its address and callers keep working. Its secrets, previews and GitHub link go with it, and its calls count in the new workspace from then on. A name under the old workspace's own domain stays behind with that domain, and an exact domain of the server's is checked again in the new workspace. A deploy key keeps working if whoever made it can deploy in the new workspace; the rest stop.
The new workspace needs room for another server on its plan, and a server can't move while a deploy is building.