Overview
A group is a named collection of users — typically aligned with a team, department, or responsibility. Instead of sharing a project with 15 individual users, share it with a group.
When someone joins or leaves the group, their project access updates automatically.
Groups only control project membership. They do not affect roles or permissions — each user retains their individual role regardless of which groups they belong to.
Creating a group
Navigate to Workspace → Groups and select Create a new group.
Enter a title and description (both required).
Add members from the workspace user list.
Optionally select projects the group should have access to.
Save the group. It now appears in the groups list with its description and member count.
Managing groups
From the groups list, use the actions menu on any group to:
View — see current members, add new ones, or remove existing members
Edit — update the group's title or description
Delete — remove the group entirely
Deleting a group does not deactivate or remove the users in it. You'll be offered the option to move members to another group before deletion, or you can skip that step.
Using groups for project access
Groups integrate with project access control in two places:
During project creation — when setting up a new project, select "Add members from a specific group" to grant the entire group access immediately.
After project creation — in the project's Settings → Access control tab, share a private project with a group. All current and future members of that group gain access.
We recommend using groups as the primary way to manage project access. It's far easier to maintain a few well-named groups than to manage per-user access across dozens of projects.
FAQ
Can a user belong to multiple groups?
Yes. Their project access is the union of all groups they belong to, plus any projects shared with them individually.
Do groups affect test run assignments?
No. Groups only control project visibility. Test run assignments are per-user.