What is recorded
Audit events cover security-sensitive and business-critical changes: role and permission changes, integration and credential changes, agent prompt, tool and knowledge changes, workflow publication, campaign launches, policy changes and support access sessions.
| Field | Purpose |
|---|---|
| Actor | User, service account or AI agent, with role |
| Tenant, target, action, outcome | What happened and to what |
| Reason and approval IDs | Why, and who approved it |
| Correlation ID | Links the event to traces, workflows and conversations |
| Before and after references | What changed, with sensitive values redacted |
Protected by design
Audit records are append-only. Application roles cannot update or delete them, access to the audit log is itself audited, and exports are controlled. Tamper evidence and SIEM streaming are available for enterprise needs.
Observability
Every request carries a correlation ID through the API, queues, integrations, AI calls and telephony. Metrics and alerts cover error rates, latency, queue age, dead letters, provider errors, call quality, AI cost and tenant limits. Sensitive data is redacted before telemetry leaves the platform.
Customer-visible access reports
If platform staff ever access your tenant, you can see who, when, why and for how long.