group.* events
Group create / update / member-sync / delete. Growth-tier only.
Groups bundle collaborators for access control: a named permission set that several people in a team share, and someone can be in more than one. They are not a way to bundle projects.
Events
group.created
New group created.
group.updated
Group renamed or re-permissioned.
group.members_synced
Who is in the group changed, with the deltas.
group.deleted
Group deleted; everyone in it loses what it granted.
| Event | Fires when |
|---|---|
group.created | A new group is created. |
group.updated | A group is renamed, or its permission set is replaced. |
group.members_synced | The people in a group changed. Carries added_ids and removed_ids. |
group.deleted | A group is deleted. Members stay in the team but lose whatever it granted. |
See the dedicated pages above for full payload, field reference, and caveats per event.
Renaming and re-staffing are separate events
group.updated covers what the group is; group.members_synced covers who
it applies to. A consumer mirroring access control needs the second one —
before it existed, changing who a permission set applied to announced nothing
while renaming the same group announced itself.
Example payload
{
"id": "evt_01HX...",
"type": "group.updated",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": null,
"data": {
"team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",
"group_id": "1f68d92a-04c5-4e83-97b1-3d6a05e2f847",
"code": "core-community",
"name": "Core Community"
}
}project_id is always null for group.* events — these are account-level.
Required abilities
Tokens subscribing to group.* events must carry group:view.
How is this guide?