group.* events
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.
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. Creating and updating a group are Growth-tier capabilities; deleting is not, and a member sync is gated only when it adds somebody.
Renaming and re-staffing are separate events.
group.updatedcovers what the group is;group.members_syncedcovers 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.
Background
Example envelope
{
"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 ability
Tokens subscribing to group.* events must carry group:view at mint time.
Events
How is this guide?
Last updated on