Groups

Groups are workspace-scoped sets of users that can be attached to projects with a role.

Why groups

For "the QA team should be able to edit test cases in every project" patterns. Manage one group's membership in one place; attach it to many projects.

Attaching a group to a project

In Project Settings → Access & Members, the Groups section (below Members) lists attached groups with their role. Attach a group by picking it and a role — one of the built-in Owner / Member / Viewer roles or any custom role defined in the workspace.

Everyone in the group gets that role's permissions on the project, in addition to any direct role they hold — effective permissions are the union of both (see Permissions model).

Detaching

Hover the group row and click the trash icon. Members of the group lose group-level access immediately. If they have direct membership too, that's preserved.

Permissions on groups themselves

Groups are created and their membership managed by a global admin in the admin console. Project administrators can attach existing groups to their project but cannot create or modify the groups themselves.