> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aient.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# team.invitation_accepted

> CloudEvent fired when a teammate accepts an Aient team invitation, with payload fields invitationId, memberUserId, and organisationId.

# ai.aient.team.invitation\_accepted

> Generated from `@aient/events`. Do not edit this page by hand.

A team invitation was accepted.

## Delivery Contract

| Field            | Value                                                                        |
| ---------------- | ---------------------------------------------------------------------------- |
| Visibility       | Tenant-selectable public event                                               |
| Topic            | `v1.events.teams`                                                            |
| Bounded context  | `team`                                                                       |
| Source           | `https://aient.ai/api/organisations/{organisationId}`                        |
| Subject          | `team/invitations/{invitationId}`                                            |
| Schema ID        | `sch_01J8X7AKZP4N6QHF2T1Y3R5V93`                                             |
| Immutable schema | `https://registry.aient.ai/schemas/sch_01J8X7AKZP4N6QHF2T1Y3R5V93.json`      |
| Version alias    | `https://registry.aient.ai/events/ai.aient.team.invitation_accepted/v1.json` |

## Payload Fields

| Field            | Required | Type     | Enum |
| ---------------- | -------- | -------- | ---- |
| `invitationId`   | yes      | `string` | -    |
| `memberUserId`   | no       | `string` | -    |
| `organisationId` | yes      | `string` | -    |

## Privacy Notes

ID-first customer-facing payload. Do not include secrets, tokens, raw telemetry, prompts, logs, or customer content.

## Lifecycle Notes

Emitted after the owning bounded-context state transition commits through its Restate handler.

## Compatibility Notes

Backward-compatible schema changes may add optional fields; removing fields, changing field types, or removing enum values requires a new schema revision and migration plan.

## Example CloudEvent

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "data": {
    "invitationId": "invitation_example",
    "memberUserId": "member_user_example",
    "organisationId": "11111111-1111-4111-8111-111111111111"
  },
  "datacontenttype": "application/json",
  "dataschema": "https://registry.aient.ai/schemas/sch_01J8X7AKZP4N6QHF2T1Y3R5V93.json",
  "id": "evt_01J8X7AKZP4N6QHF2T1Y3R5VAA",
  "organisationid": "11111111-1111-4111-8111-111111111111",
  "source": "https://aient.ai/api/organisations/11111111-1111-4111-8111-111111111111",
  "specversion": "1.0",
  "subject": "team/invitations/invitation_example",
  "time": "2026-04-25T12:00:00.000Z",
  "type": "ai.aient.team.invitation_accepted"
}
```