Groups
Grant a set of permissions to several members at once, on top of their roles, and keep the group's membership in step with the team.
By the end of this page you will know when a group is the right tool, how to create one and choose who is in it, and what its members gain.
A group is a named set of permissions handed to several members of one team at once. A member keeps their role and gains whatever their groups grant on top of it. Groups suit the cross-cutting cases a role does not fit: the release crew drawn from developers and QA, the people who may approve on a project manager's behalf, the handful who manage integrations.
Before you begin
| You need | Why |
|---|---|
group:view-any | To see a team's groups on the page. The owner always can. |
group:create | To create a group in a team. |
group:update | To edit a group's name or permissions, or pick its members. |
group:delete | To delete a group. |
Where groups live
Open Account Settings → Groups. The page lists the groups of every team where your role lets you view them, newest first:
| Column | What it shows |
|---|---|
| Group | The name, with the code in small type. |
| Team | Which team the group belongs to. |
| Permissions | How many permissions the group grants. |
| Members | How many people are in it. |
| Row menu | Members and Edit when you may update groups in that team, Delete when you may delete them. |
Create a group
- Press Create a Group. The button appears when at least one of your teams lets you create groups.
- Pick the Team, type a Name and a Code, and tick the Permissions the group grants.
- Press Create. The group starts empty; add people from its row menu.
The code must be unique within the team and is fixed once created, for the same reason a role's code is.
Choose the members
- Open the group's row menu and choose Members.
- Tick the people who should be in the group. The list holds the owner and every member of the group's team, with their addresses, and the people already in the group are ticked.
- Press Save Members. The confirmation says how many were added and how many removed.
Only people already in the team can be in one of its groups. Someone outside the team is refused rather than quietly dropped, so a mistake never reads as a save that did less than it said.
Saving replaces the membership with exactly what is ticked. To take one person out, untick them and save.
Edit a group
- Open the row menu and choose Edit. The code is shown but not editable.
- Change the Name or the Permissions and press Save.
- The group's members gain or lose the permissions the next time they load a page.
Delete a group
- Open the row menu and choose Delete, then press Delete Group.
- Its members keep their roles and lose only what the group granted.
All the fields
What happens next
Groups announce nothing to webhooks today; their effect shows in what members may do. A member's effective permissions are their role's set joined with the sets of every group they are in, and a permission check anywhere in the product reads that union.
Permissions
| Action | Who may do it |
|---|---|
| See a team's groups | The owner, or a member with group:view-any |
| Create a group | The owner, or a member with group:create |
| Edit a group or its members | The owner, or a member with group:update |
| Delete a group | The owner, or a member with group:delete |
Frequently asked
Related
- Roles: the permission catalogue and the one role each member holds.
- Members and guests: who can be in a group.
How is this guide?
Last updated on
Ability Reference
The complete list of permissions a role or a group can grant, what each entity covers, and a plain sentence on what a member holding each permission can do.
Activity Log
Read every change recorded in your team, see who made it and whether it came from a person, a token, an agent, an integration or the system, and open an item's full history with its field-by-field changes.