Members & roles

Project access is governed by project roles — separate from global roles.

Roles

• OWNER — can edit settings, members, custom fields, trees, tokens; can delete the project.
• MEMBER — can author and run test cases and launches; cannot change settings.
• VIEWER — read-only.

In Allure terms: VIEWER ≡ Read, MEMBER ≡ Write, OWNER ≡ Owner.

Effective role

A user's effective role is the maximum of:

• Their direct ProjectMember.role, if any.
• The role granted by every group they belong to that's attached to the project.

So a VIEWER who's also in a group attached as MEMBER is effectively a MEMBER.

Adding a member

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

In Project Settings → Access, click Add member and pick someone who's already in the workspace, then assign their project role (Owner / Member / Viewer). 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 (Owner-only access).