> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwacks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Team & roles

> Invite people to your studio and control what they can do with roles.

A studio is rarely one person. **Team management** is where you bring people into the active
studio, set what they're allowed to do, and remove them when they leave. Everyone you add belongs
to *this* studio only — the same person can hold a different role in another studio.

Team management is available to **admins and managers** — the roles that can change who's in the
studio. Editors and viewers don't have access to it.

## Roles

A member's **role** decides what they can touch. There are four studio roles:

| Role        | In the apps  | Manage team | Studio settings | Billing |
| ----------- | ------------ | ----------- | --------------- | ------- |
| **Admin**   | Read & write | ✓           | ✓               | ✓       |
| **Manager** | Read & write | ✓           | —               | —       |
| **Editor**  | Read & write | —           | —               | —       |
| **Viewer**  | Read only    | —           | —               | —       |

Put simply: **admins** run the studio and are the only role that touches billing and studio
settings; **managers** handle the team and the day-to-day work; **editors** do the work but don't
manage people or the account; **viewers** look without changing anything.

<Note>
  Roles are per-studio. The same account can be an admin in one studio and a viewer in another —
  switching studios switches the role you're acting with.
</Note>

## Inviting people

Invite a member by email and choose the role they should start with. They receive an invitation;
once they accept — creating a Qwacks account first if they don't already have one — they appear in
your members list with that role. You can change someone's role or remove them from the studio
whenever you need, and the list can be searched by email or filtered by role as the studio grows.

## Specialized testing roles

Protokite playtesting adds two narrower roles — **QA** and **Play Tester** — for people who only
take part in tests. They're scoped to test participation rather than running the studio, so they
don't carry the studio-management permissions above. You'll come across them when assigning testers
in Protokite.