Members & roles

Project access is governed by project roles — separate from account and workspace roles. A project role is a named set of permissions; see the permissions model for the full catalog.

Roles

• Owner — every permission: content editing, deletion and permanent deletion (Purge), and project administration (settings, members, custom fields, trees, tags, webhooks, integrations).
• Member — creates and edits test cases, launches, test plans, and defects, and restores from Trash; cannot delete, purge, or change project settings.
• Viewer — read-only. Sees every area of the project (Trash excluded), changes nothing.
• Custom roles — any role defined in Workspace Settings → Roles can be assigned here too.

Effective permissions

A user's effective permissions are the union of every role they hold on the project:

• their direct member role, if any,
• the role of every group attached to the project that they belong to, and
• the project's default access role, when one is set in Project Settings → General.

Each role contributes its permission set — there is no role ranking. A direct Viewer who is also in a group attached with the Member role can do everything a Member can.

Adding a member

People join the workspace first, then get added to individual projects.

In Project Settings → Access & Members, click Add member and pick someone who's already in the workspace, then assign their project role. To bring in someone who isn't in the workspace yet, invite them at the workspace level first — see Invitations.

You can also attach a whole group to the project with a role, below the members list.

Removing a member

Hover the member row and click the trash icon. The user loses direct access immediately. If they're in a group attached to the project, they keep group-level access.

Audit

Every membership change is recorded in the project's membership audit (visible to project administrators).