Groups
Groups let you manage project membership for collections of users (teams, departments, vendors). Assign roles once to the group and every member inherits them automatically.
Creating a group
Provide:
- Name – e.g., “Mobile QA”, “Contractors”, “Customer Success”.
- Members – Pick existing users (SSO and local accounts supported).
Applying groups to projects
- When editing project access, add the group and choose the project role they should receive.
- Members inherit the group role; you can override an individual by assigning them a different role directly.
- Removing a member from the group revokes their group-derived access from every project.
Best practices
- Mirror your organisational structure so onboarding/offboarding is painless.
- Pair groups with SSO auto-provisioning: once a user is added to a group in your IdP, sync them into the equivalent TestFish group.
- Use groups for automation tokens if multiple pipelines share the same permissions (create a “CI Pipelines” group and assign the integration role).