> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/ai-video/team-management.md).

# Team Management

## Seats & Pricing

### How do seats work on AI Video?

* **Free** — 1 seat.
* **Pro** — up to 10 seats included, at no extra cost. Price depends only on your monthly AI-credit allowance (see Plans, Credits & Pricing) — never on how many of your 10 seats are filled. One member or ten, the price is the same, and there's no self-serve way to add seats beyond 10 on Pro.
* **Enterprise** — no seat limit enforced in the product; seat count is negotiated as part of your contract.

### Who counts toward Pro's 10-seat limit?

Everyone, regardless of role — Owner, Admin, Editor, Collaborator, Viewer, and Billing User all count equally toward the 10. This is different from Interactive Demo's Growth plan, where Viewers and Billing Users don't count toward its seat limit — on AI Video, they do. Anyone invited but not yet accepted (pending, nominated, or requested) also occupies a seat until they're removed or decline.

### What happens if I try to invite an 11th member on Pro?

Usually you won't get as far as the invite form: once a workspace has 10 seat-holders, the Invite button is replaced with a prompt pointing you to sales instead of the normal invite flow. If a request does reach us — for example, inviting several people at once — it's refused with a message pointing you to sales for more seats. Either way, nobody already in the workspace is removed or demoted — only new invites are blocked.

### How do I get more than 10 seats?

Enterprise is the only path — seat count becomes part of your negotiated contract, with no limit enforced in the product. [Talk to our sales team](mailto:sales@arcade.software).

***

## Inviting & Roles

### Who can invite new members?

* **Owner** and **Admin** can invite someone directly, choosing their role — the invite goes out right away.
* **Editor**, **Collaborator**, and **Billing User** can request that someone join, which then needs an Owner or Admin to approve before it takes effect.
* **Viewer** can't invite or request anyone, and can't open the Members page at all.

### How do I invite someone to my AI Video workspace?

From the video settings menu, go to **Members**, then invite by email — you can enter several at once, and an Owner or Admin additionally picks what role to assign. This is the same invite flow used across Arcade.

### What happens after I send an invite?

If the person already has an Arcade account, they're added right away and notified by email. If they don't have one yet, they get an email invite link that takes them through sign-up and straight into your AI Video workspace.

### What roles are available?

AI Video uses the same workspace roles as the rest of Arcade, since both products share one workspace/account system: **Owner**, **Admin**, **Editor**, **Collaborator**, **Viewer**, and **Billing User**. Owner isn't assignable through an invite — it only moves with a separate ownership transfer.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arcade.software/kb/ai-video/team-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
