Skip to main content
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:
RoleIn the appsManage teamStudio settingsBilling
AdminRead & write✓✓✓
ManagerRead & write✓——
EditorRead & write———
ViewerRead 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.
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.

​
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.