team.* events
Team creation, rename and deletion, and the comings and goings of the people in it.
Team creation, rename and deletion, and the comings and goings of the people in it. A team is the tenant every token is scoped to, so these are account-level events: project_id is always null and an endpoint confined to a project never receives them.
Background
Example envelope
{
"id": "evt_01K8QD4N3M7Y2K4N6P9R1T3V70",
"type": "team.member_joined",
"created_at": "2026-11-03T14:22:00+00:00",
"api_version": "2026-11-01",
"project_id": null,
"data": {
"role": "developer",
"team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",
"user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80"
}
}data is flat and deliberately thin: ids, role codes, plus whatever the transition itself carries. It is not a snapshot of the team or the person. Read the team members endpoint for the profile, which keeps a member's email behind the team-member:view ability. The one exception is team.member_invited, which carries the invitee's email: an invitee has no user record to look up yet, so the id-only rule cannot apply to it.
Required ability
Tokens subscribing to team.* events need team-member:view-any at mint time, the ability that lists a team's roster, for all seven events.
Events
team.createdA team is created.team.updatedA team is renamed.team.deletedA team with no projects is deleted.team.member_invitedAn invitation is sent to a staff member or a client guest.team.member_joinedAn invitee accepts and becomes a member.team.member_removedA member is removed from the team.team.member_role_changedA member moves to another of the team's roles.How is this guide?
Last updated on