Workspace and members

A workspace is the container everything else lives inside. It holds your team (the members), your money (the billing and credits), your inbound phone numbers, your programmatic API keys, and your agents. When you sign up you get one workspace; you can create more, and a person can belong to several at once.

The workspace is also the unit of access. Membership is what grants you access to the agents inside it: if you are a member of the workspace, you can see and work on its agents, subject to your role. Nothing in the product is owned by a single person. It is owned by the workspace, and members act on it.

What a workspace owns

One workspace can hold many agents, and everything those agents share is held at the workspace level:

• Members and their roles (this page).
• Billing and credits. A single balance and subscription fund every call and every agent in the workspace. See Billing and credits.
• Phone numbers. Numbers live in a workspace pool, then get assigned to an agent. See Phone numbers.
• API keys. Programmatic access to the workspace and its agents, for the public API and for Claude Code.
• The agents themselves. Each agent is workspace-scoped. The capabilities an agent carries, its prompt, tools, and knowledge base, belong to that agent, but the agent belongs to the workspace.

Every agent is addressed by a handle of the form workspace-slug/agent-slug, so the workspace slug is part of the identity of everything inside it.

Members and roles

Each member of a workspace has exactly one role. The role decides what the member is allowed to do across the whole workspace. There are four roles: owner, admin, editor, and viewer.

The permission model is deliberately simple. Two groups of people can do the sensitive things:

• Owner and admin can manage the workspace: billing, members, workspace settings, API keys, audit logs, and workspace-wide skills and connectors.
• Owner, admin, and editor can build: create and edit agents, and contribute their own skills and connectors.

A few details behind the table:

• Owner is the workspace's single legal and billing contact. There is always exactly one. The owner can do everything an admin can, plus transfer ownership and delete the workspace.
• Admin is the day-to-day administrator. Admins manage members, billing, settings, and keys, and they build agents. They cannot delete the workspace or take the owner role unless the owner hands it over.
• Editor is the builder role. Editors create, edit, and publish agents, but they cannot touch members, billing, settings, or keys.
• Viewer is read-only. A viewer can see the workspace and its agents but cannot change them.

These rules are enforced on the server, not just in the screen you see, so the same limits apply whether a member acts through the app, the public API, or Claude Code.

Inviting and removing members

You manage members under Settings in the workspace, in the Members section. Inviting and removing members needs the owner or admin role.

Inviting

Invite a member by email and pick their role. What happens next depends on whether that email already has an account:

• Already has an account. They are added to the workspace straight away and get a notification email.
• New to the platform. They get an invitation email with a link. Opening the link lets them set a password, create their account, and join. The link stays valid until they accept it, so it is safe to forward.

Every workspace has a seat limit tied to its plan. A seat is an active member or a pending invitation. When the workspace is at its limit, a new invite is refused and you are pointed at sales to add more seats. See Billing and credits for what your plan includes.

Changing a role

An owner or admin can change any member's role in the Members section. One rule protects the workspace: it can never be left without an owner.

• To make someone else the owner, the current owner promotes them. This is a single-owner handover: the moment the new owner is set, the old owner is moved to admin automatically. Only the current owner can do this.
• You cannot demote the last owner. Hand ownership over first, then change the old owner's role if you need to.

Removing members and leaving

• Removing someone else needs the owner or admin role.
• Leaving yourself is open to any member; you do not need a special role to leave a workspace.
• The owner cannot be removed or leave while they are the last owner. Transfer ownership to another member first.

Workspace settings

Workspace settings, under Settings, are owner and admin only. The two that shape how the workspace is identified:

• Name. The workspace's display name. Changing it is cosmetic; nothing that points at the workspace breaks.
• Slug. The workspace's stable identity in URLs and in every agent handle (workspace-slug/agent-slug). A slug is lowercase letters, numbers, and hyphens, and must be unique across the platform.

The same settings area is where you manage data and privacy policy for the workspace, such as transcript retention and PII scrubbing. See Privacy for what those controls do.

API keys

An API key gives a program, rather than a person, access to the workspace and its agents. Keys are what the public API and Claude Code authenticate with. They are workspace-scoped: a key acts inside the one workspace it was created in.

You manage keys under Settings, in the API keys section. Creating and revoking keys needs the owner or admin role.

Creating a key

Give the key a name that says what it is for, then create it. The full key, which starts with vai_, is shown once at creation. Copy it then and store it somewhere safe, because afterwards only its short prefix is ever shown again. There is no way to recover the full key later; if you lose it, revoke it and create a new one.

Revoking a key

Revoke a key the moment it is no longer needed or might have leaked. Revoking is immediate: any program using that key stops working at once. Revoking one key does not affect your other keys.

Scopes

When a key is used to drive the agent API, its access is bounded by coarse scopes that map onto what each call is allowed to do:

Scopes are the coarse filter; the workspace's own access rules are the authoritative bound underneath them, so a key can never reach beyond the workspace it belongs to. For setting a key up for use with Claude Code, see Claude Code setup.

How this relates to agents and billing

The workspace is the hinge between your team and your product:

• Agents are created and edited by owners, admins, and editors, and viewed by everyone in the workspace. Read Agents for what an agent is and how it is built.
• Billing and credits are managed by owners and admins, and the balance funds every agent and every call. Read Billing and credits.
• Phone numbers are bought into the workspace pool, then assigned to an agent. Read Phone numbers.

If a term here is unfamiliar, the glossary defines workspace, member, role, and the rest.