All articles

Team workspaces

A team workspace sits beside your personal one rather than inside it. You switch between them from the workspace menu, and nothing crosses over on its own — the merge most people expect never happens. Your personal projects stay personal; everything the team makes belongs to the team, including after you leave.

What a team workspace is

A team workspace has its own projects, its own files, and one pool of credits that every seat pays into. Your personal workspace stays exactly as it was, permanently yours, with no members, no invitations and no seats to manage.

The creating is the same — same generators, same editors, same agent. What changes is who can see the work, whose credits pay, and who may edit at any one moment.

Note
In a team workspace you generate inside a team project, not from the workspace home. Where a tool isn't available in team projects yet, the app says so.

Seats, the shared pool and invitations all start once the team's first payment goes through.

What is shared, and what stays yours

Shared with the teamYours alone
Projects and their documentsYour private chat with the agent
The project's files and published assetsYour view of a project: zoom, scroll, open document, selection
The credit pool and any top-upsThe AI agents you connect over MCP
Usage, which Admins can see per memberYour personal workspace and its library

Private chat really is private: an Admin can't read another member's conversation with the agent. Bringing work across goes one way — an item from your personal library can be copied into a team, where it becomes a team asset, but team assets can't be registered back into your personal library.

Seats, roles and invitations

There are two roles, and both take a seat:

  • Admin — manages members, seats and billing.
  • Member — generates from the shared pool.

A team always keeps at least one Admin. Admins invite people by email from the Members tab of workspace settings, choosing the role as they send.

A pending invitation holds a seat until it is accepted, revoked or expires — so a team can run out of free seats before anyone has joined. Accept an invitation with the address it was sent to; signed in as someone else, the invite page offers to switch rather than quietly joining as the wrong person.

Seats are bought and changed in Billing. Added seats take effect and are charged straight away; a cut takes effect at renewal, when all seats renew together. The fewest seats each plan allows, and the most a team can have, are shown where you buy them.

How the shared credit pool is spent

Every seat adds its plan credits to one pool each month, and everyone draws from it — so one person's long video is credits another no longer has. Admins can top the pool up; those credits land immediately and, unlike a personal account's, end with that month's credits instead of rolling over.

Admins can also give any member a monthly limit and pause their spending:

  • A limit caps what one member can draw from the pool, and can't be set below what they've used this month. A member at their limit is told; an Admin raises it in Members.
  • A pause stops a member spending the team's credits, but does not take away their editing.

The Usage tab shows each member's usage, split between web and MCP, and their share of the pool. Failed and cancelled generations return to the pool as they would to a personal balance — see Credits and plans.

What happens when two people open the same project

One person edits a project at a time, and the lock covers the whole project, not one document in it. Opening a project someone else is editing doesn't drop you into a silent read-only view: you're told who has it, and offered a choice:

  • Take over — you become the editor, starting from the state you're looking at.
  • Back to home — leave it with them.

If an agent was running for the person you took over from, taking over stops it, and whatever it made stays. The lock catches you too: your own second tab or your own agent holds it the same way, named as yours so you can take it back.

Lose the lock partway through an upload, a rename or a generation and you're told it didn't happen, rather than having it applied later.

Leaving, removing someone, or closing a team

Leaving a team takes effect immediately: you lose its projects and its pool, and an Admin has to invite you back. What you made there stays with the workspace.

Removing a member is also immediate, but their seat stays paid until seats are cut at renewal — so it doesn't shrink the bill straight away.

Only Admins see Billing, where the payment method and invoices sit with the payment provider and the plan can be cancelled. A team with no plan and nothing in it can be removed outright; anything else is a cancellation, not a deletion.

Need more than a team plan covers? See Enterprise.

Related articles