A workspace is one account's view of the dashboard — its keys, its usage, its plan. You always have your own, and you get access to another one when someone invites you to theirs.
The switcher in the dashboard header moves you between them. There is no limit on how many you can belong to, and your own is always in the list.
Knowing where you are
While you are in someone else's workspace a dark context bar sits above the page: whose workspace it is, whether you have View only or Admin access, and a Leave workspace button that drops you straight back to your own.
It is deliberately styled unlike the usage banner, because it describes a mode you are operating in rather than an alert. It appears on every page except the three where it would be redundant or misleading — Teams, where you manage this in the first place, and Browse and GraphQL, which behave identically no matter whose workspace you are in.
If you are ever unsure what account you are about to change something on, that bar is the answer.
What switching changes
Everything belonging to an account follows the switch: the API keys and sub-keys, the analytics and call log, the plan and its ceilings, the VerveKit tools.
What does not follow the switch is you. Your login, your profile, your notification preferences and your two-factor settings stay yours in every workspace — which is why the settings page is read-only in a workspace you do not own, for admins as well as viewers, and why the Security tab is not there at all. Personal settings belong to a person, not to a view.
Three pages redirect rather than render, because there is nothing meaningful to show:
| Page | In someone else's workspace |
|---|---|
| Plans | Redirects to Billing |
| Billing | Explains that only the owner manages billing |
| Referrals | Redirects to the overview — referrals are personal, and yours do not follow you |
What you can do there
Your role in that workspace decides it.
As a viewer, everything is visible and the controls are disabled. As an admin, you can operate the tooling — mocks, bins, forms, the AI Assistant, the audit export on Mega.
Neither role can manage keys. Rotating a key, creating a sub-key or editing restrictions is refused for anyone who is not the owner — Only the workspace owner can manage keys — so an admin seat is genuinely about running the tools rather than holding the credentials. See roles.
The AI Assistant is the one tool a viewer cannot open at all: Switch to your own workspace to use the AI Assistant. Token allowances belong to an account, and spending someone else's on a read-only seat would be odd. See AI Assistant.
Whose credits a call spends
This is the thing to internalise before you run anything, and it is not quite "the workspace pays".
Where a key can be picked, a shared workspace shows two groups — Your keys and the owner's workspace — and the selected key carries a pill saying which it came from. The call is billed to whichever key you picked, not to whichever workspace you are looking at.
So both are possible, on purpose:
- Their key — the call comes out of their allowance and shows up in their analytics. Correct when you are debugging their integration.
- Your key — the call comes out of yours, in their workspace, against their data. Correct when you are trying something for yourself and happen to be looking at their account.
Everywhere outside the playground, a call is made by whatever key you put in it. A workspace is a view; a key is what actually pays. The habit worth forming is reading the pill before you press run — a viewer with no write access can still spend an account's credits one call at a time.
Leaving a workspace
You can leave one you were invited to, at any time, from the teams page, and the Leave workspace button on the context bar only returns you to your own view — it does not end your membership.
Leaving ends access immediately and frees the owner's seat. Nothing about your own account changes, and the owner can invite you again — with no cooldown, since leaving removes the invite record entirely.
If the owner removes you instead, the effect is identical and equally immediate: the workspace simply stops appearing in your switcher, and anything you had open there stops working.
Before you leave, note that you lose access to everything in it. If you were relying on a key you read from that workspace, that key still works — it is a credential, not a permission — but you will not be able to look it up again.
Your own workspace
Always there, always yours, and it is where anything personal happens: your password, your two-factor, your notification preferences, your referrals, your own keys and plan.
If a control you expect is disabled or missing, the first thing to check is which workspace you are in. The second is your role in it.
Next
Roles explains what each role can do, invites covers getting access, and teams is the overview.