What is scoped to a workspace
Providers and their keys. Enabled models. API keys. Mappings and prompts. Quota rules and the spend budget. Workflows. Website indexes. Metrics. Two things are not scoped to a workspace: your plan, which is per account and so shared across all of them, and your credit balance, which is a single account wallet. That distinction matters. Ten workspaces do not give you ten times the requests per minute. They give you ten separate configurations sharing one budget.Switching
The workspace picker sits at the top of the console sidebar. Your default workspace is the one you land in when you sign in. If a workspace you were in is deleted, the default moves to your most recent one.The Team section
Open Team in the console sidebar. It has four pages, and each one shows the workspace you have selected.
Members see their own actions in the audit log. Anyone holding “View all
usage” sees everyone’s, which by default means owners and admins.
Members and roles
These are the defaults. The owner can change what Admin and Member may do, and
add more roles, under Team, Roles.
Removing someone from a workspace also turns off every API key they made in it,
so a former member cannot keep spending the workspace’s providers.
There is exactly one owner. You can change or remove only people ranked below
you, so an admin can manage members but never another admin and never the
owner. Making someone an admin needs a rank above the Admin role, which by
default means the owner. Nobody can change their own role.
Custom roles
Roles work like they do on Discord. Everyone holds Member. Admin and any role you create add permissions on top of it, and a person’s permissions are everything their roles allow together.
Permissions are grouped by area: keys, providers, models, quotas, prompts and
mappings, workflows and indexes, usage, team, and workspace. A workspace can
have up to 25 extra roles. Assign them to people under Team, Roles,
People. Admin itself is still set on the Members page.
Keys always belong to the person who made them. “Create and manage own keys”
never lets anyone edit someone else’s key.
What each role sees
Seeing a provider, model, key or quota rule is not the same as changing it.
Those four can only be edited, switched on or off, or deleted by the person who
created them, so an admin sees other people’s rows without the edit and delete
buttons. The console only shows the create, edit and delete buttons a role is
allowed to use.
Inviting people
An invite is a code, not an email. Create it under Team, Members, then send the link yourself.
Only the owner can create a link that is both unlimited and never expires.
Opening an invite link shows the workspace name and a Join workspace button.
Nothing changes until you press it, and joining needs a verified email.
Restricting an invite to one or more email addresses means only an account with
one of those addresses can redeem it. Revoking an invite stops it working
immediately, even if it was already sent. When the person who created an invite
leaves or is removed, their invites stop working too.
The member cap comes from the plan, and an invite is refused at creation time
if the workspace is already at it.