Roles and permissions
Magister has two layers of roles: at the team level and at the project level. Team roles apply to everything the team owns; project roles only apply inside one project.
Team roles
Team Owner — has every permission, including the one thing admins can't do: delete the team. Every team has exactly one owner by default (the person who created it).
Team Admin — can manage team settings, manage billing, create and delete projects, invite members, manage integrations for any project, and view all chats across projects.
Team Member — can use projects they've been added to. Cannot manage billing, invite members, or change team settings.
Project roles
Project Admin — can manage the project's settings, connect or disconnect integrations for that project, and manage project members. Team owners and team admins automatically have this level inside every project.
Project Member — can chat with the agent, run workflows, upload files, and use the project normally. Cannot change project settings or connect integrations.
Rule of thumb — if it touches billing or the team itself, you need to be a team owner or admin. If it touches a specific project's config, you need to be a project admin (or higher). Day-to-day chatting and running workflows only needs member.