Home / Knowledge Base / Understanding Roles and Permissions
Understanding Roles and Permissions
QAM Hub uses role-based access control at two levels: organization roles and project roles. This lets you give people broad control over the whole organization, or scoped access to a single project, depending on what they need.
Organization roles
- Organization Admin — manages the organization: users, projects, and organization-wide settings.
- Member — belongs to the organization and is granted access to specific projects through project roles.
Project roles
Within each project, a user holds one of three roles:
- Project Admin — full control of the project, including settings, custom fields, and member access.
- User (executor) — creates and edits test cases and executes test runs.
- Viewer — read-only access; can see test cases, runs, and reports but cannot change them.
How to choose the right role
As a rule of thumb: give QA engineers who run day-to-day testing the User role, give leads who manage project configuration Project Admin, and give stakeholders who only need visibility the Viewer role. Reserve Organization Admin for people who manage the account itself.