User groups

Use groups to grant project access to a whole team at once, and to delegate who manages the team.

User groups let you grant access to a whole team in one move instead of person by person. The point is leverage: you give the group a role on a project (in Permissions), and everyone in the group inherits it — so when someone joins or leaves the team, you change the group once and every project they touch updates automatically.

When to use a group vs. an individual

Reach for a group whenever the same set of people should have the same access to one or more projects — a service team, a customer’s staff, an on-call rota. Assign an individual directly only for genuine one-offs. If you find yourself granting the same person the same role on project after project, that’s a sign they should be in a group instead.

Delegating who runs the group

Within a group, a member is either an admin or a plain member. This isn’t about project access — both get the group’s project roles — it’s about who can manage the membership. A group admin can add and remove members of that group without being a system administrator, so you can hand a team lead control of their own team while keeping overall administration locked down.

Putting groups to work

1. Create the group with a clear name (and a description so others know what it’s for).
2. Add its members, marking the team lead(s) as group admins.
3. In each relevant project’s Permissions, grant the group the roles it should have.

From then on, membership is the only thing you maintain — the access follows.