Every action a control plane operator takes — provisioning, suspending, decommissioning a tenant, inviting an org member, editing a plan — emits an OrgEvent to the audit log. The audit feed is the system-of-record for "who did what, and when" at the platform layer.
This page lists the events, what they mean, and what payload they carry. The wire shape is stable; new event types are additive.
Read the audit feed
The control plane admin console's Audit page is the primary surface — see Read the audit log. For programmatic access the events surface is documented under Reference — API.
Each event row carries this shape:
interface OrgEvent {
id: string // ULID, monotonic per org
type: OrgEventType // enum below
actor_id: string | null // user id; null for system events
actor_email: string | null // best-effort denormalised email
org_id: string
tenant_id: string | null // present when the event scopes to a tenant
data: Record<string, unknown>
created_at: string // ISO 8601, UTC
}
Event types
The type field is a closed enum following the <entity>.<action>.<phase> convention so consumers can prefix-filter cleanly. New types ship in versioned platform releases; existing types never rename.
Tenant provisioning saga
The provisioning workflow emits per-phase events so the audit feed reads as a chronological narrative of the saga's progress.
Type | Emitted when | Payload includes |
|---|---|---|
| A platform operator submits a provisioning request and the workflow row is written |
|
| A saga activity completes (one event per step — validate, allocate, schema, deploy, etc.) |
|
| A saga activity failed but the workflow is still inside its retry budget |
|
| Provisioning succeeded and the tenant is now Active |
|
| An activity fails after retries; the compensation chain has run |
|
| A compensating activity has started while unwinding a failure |
|
| A compensating activity ran during failure or cancellation recovery |
|
One event is still being wired
tenant.provisioning.cancelled is documented here as the canonical event for an operator-initiated cancel from the tenant detail page, but the saga doesn't emit it yet. Today, a cancel surfaces as the compensation events (tenant.provisioning.compensating / tenant.provisioning.compensated) followed by the final state change to Failed. The distinct cancelled event will fire from the same code path that runs cancel compensations once the emission is wired.
Reset saga (escape valve for a stuck provisioning)
Reset is a separate workflow from provisioning; it runs to clear a wedged workflow handle and emits its own three events.
Type | Emitted when | Payload includes |
|---|---|---|
| A platform operator submits a reset on a stuck tenant |
|
| Reset finished cleanly; the tenant is back in Pending with a fresh saga ready |
|
| Reset itself failed (rare; usually because cancel hadn't fully completed) |
|
Tenant deprovisioning saga
Type | Emitted when | Payload includes |
|---|---|---|
| Decommission request accepted; resource release begins |
|
| A decommission step completes (one event per step) |
|
| A decommission step failed but the workflow is still inside its retry budget |
|
| Decommission finished; resources released |
|
| A decommission step failed; partial release |
|
Update saga (plan/region/topology applied to a tenant)
The Update workflow re-applies the org's current plan to a tenant's namespace (retention, knobs). Used when the org's plan changes or when topology overrides shift.
Type | Emitted when | Payload includes |
|---|---|---|
| An update workflow starts on a tenant |
|
| The update applied cleanly |
|
| The update failed at some step |
|
Plan-upgrade saga (org plan tier flip)
The plan-upgrade workflow flips the org's plan, recomputes effective knobs, briefly holds the tenant row read-only, and bumps the data-plane cache version.
Type | Emitted when | Payload includes |
|---|---|---|
| The plan upgrade saga begins |
|
| Plan upgrade finished cleanly |
|
| Plan upgrade failed and compensations are running |
|
| A compensation step ran during plan-upgrade rollback |
|
| A compensation step itself errored — operator intervention may be required to clear stuck state |
|
Tenant lifecycle (post-provisioning)
Type | Emitted when | Payload includes |
|---|---|---|
| A platform operator pauses tenant traffic |
|
| A suspended tenant is resumed | none |
Organisation members
Type | Emitted when | Payload includes |
|---|---|---|
| A platform operator invites a new org member |
|
| An invited member accepts |
|
| A member is removed |
|
| A member's role within the org changes |
|
| A pending invitation's link was re-emailed |
|
| A pending invitation was cancelled before acceptance |
|
| The Owner role moved from one member to another |
|
Plans and policy
Type | Emitted when | Payload includes |
|---|---|---|
| A platform operator changes a tenant's plan |
|
| The platform-wide MFA default for new tenants changes |
|
Filtering at read time
The endpoint takes optional type and tenant_id query parameters. The control plane console uses these to drive the audit page filters; SIEM exports use the same shape.
GET /api/v1/organizations/{id}/events?type=tenant.provisioning.failed&tenant_id={t}&cursor=01HZX...&limit=50
What's missing from the audit feed
Three things are deliberately not in this feed:
Tenant-scoped events — what individual users did inside a tenant lives in the tenant's own audit log, not the platform feed. Access via the tenant admin console.
Read-only viewing — opening a page doesn't emit an event. Only state changes do.
Health probe results — infrastructure-level signals belong in the observability stack, not the audit ledger.