Roles, members, and seats

A Teams workspace has four roles and two kinds of seat, and the pricing follows directly from them: people who build pay, people who watch are free. This page covers what each role can do, how inviting works, and what seats cost.

The four roles

• Viewer. Read-only: can open projects and look, cannot build or spend tokens. Viewer seats are free and unlimited.
• Editor. Builds: creates projects, chats with the agent, edits code, publishes, and spends from the shared token pool.
• Admin. Everything an editor does, plus running the workspace: inviting and removing members, changing roles, workspace settings, budgets and the audit log, and approving what needs approval.
• Owner. One per workspace. Everything an admin does, plus the things that must have exactly one accountable person: billing, deleting the workspace, and transferring ownership. Transferring makes the new person owner and steps you down to admin.

A role applies across the whole workspace, every project alike.

Inviting people

Invites go by email from the workspace's Members page, and nothing is billed until the person accepts:

• Viewers are free, so anyone in the workspace can invite one.
• Editors and admins occupy a paid seat. Owners and admins invite them directly. An editor can also propose a new editor, but the invite waits as a pending approval until an owner or admin confirms the added seat; until then the recruit is not emailed and nothing is charged.

Pending invites sit in their own tab on the Members page, and the invite form tells you the billing consequence before you send.

What seats cost

Teams pricing is per paid seat, and the whole workspace picks one rung of a ladder that sets each seat's monthly token allowance:

The pool is simply seats times the rung: five editors on the $55 rung share a 25M pool. A paid seat is any active editor or admin; there is a minimum of 2 paid seats and a maximum of 10 editors (talk to us about Enterprise beyond that). Teams has no daily token cap and no daily publish limit.

Removing people and changing roles

Owners and admins change roles and remove members from the Members page. Two protections apply:

• Access ends immediately, work stays. Everything the person built belongs to the workspace.
• Their connected services are handled deliberately. If the person leaving had connected third-party services the apps depend on, Vaulter shows you what depends on them. A payment connection like Stripe blocks the removal until someone reconnects it, so a live storefront never silently loses its payment path; other connections can be acknowledged and reconnected later, and are flagged as connected by a former member until someone does.

If the plan lapses

Leaving Teams never deletes anything or throws anyone out. Members and projects stay; what shrinks is the edit surface. Paid seats above the new limit drop to read-only, and the owner chooses who keeps the remaining paid seats.

Frequently asked

Which role should clients get?

Viewer. They can watch progress in the real project, free, without any way to change or break it. If a client should use the finished product rather than watch the building, they belong in the app's own users instead, on any plan.

Can two people build in the same project at once?

The agent works on one request at a time per project: while a turn is running, a second request to the same project is refused rather than interleaved, so two people cannot corrupt a build by prompting at once. Two people in two different projects work fully in parallel.

We have more than 10 builders

The 10-editor cap is where Enterprise starts; contact us through support. Viewers never count toward it.