group.updated
Group name or membership changes.
project_id is always null for group events.When this fires
A group's name changes, or projects are added to or removed from the group.
Required ability
group:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "group.updated",
"created_at": "2026-05-22T10:05:00Z",
"api_version": "2026-05-01",
"project_id": null,
"data": {
"team_id": "tem_01HX...",
"group": {
"id": "grp_01HX...",
"code": "core-community",
"name": "Core Community"
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always group.updated for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | null | Always null — account-level event. |
data.team_id | string ULID | Team that owns the group. |
data.group.id | string ULID | Group identifier. |
data.group.code | string | Stable group code (immutable across renames). |
data.group.name | string | Updated display name. |
Caveats
- Membership detail (which projects belong to the group) is not embedded; fetch the group from the API to determine what changed.
- Group-scoped role assignments are unchanged by membership tweaks but the effective access surface changes immediately.
Related events
group.created— predecessor.group.deleted— terminal state.- Group events overview — back to family overview.
How is this guide?