Billing and usage
How an organization chooses a plan, pays through Stripe Checkout and the Stripe Customer Portal, and tracks metered usage, credits and limits on the Usage and Limits page.
Profile
How to manage your personal details, language, regional formats, theme, sign-in methods and notification channels, and which account pages live outside an organization.
Billing and usage
How an organization chooses a plan, pays through Stripe Checkout and the Stripe Customer Portal, and tracks metered usage, credits and limits on the Usage and Limits page.
Profile
How to manage your personal details, language, regional formats, theme, sign-in methods and notification channels, and which account pages live outside an organization.
How to review, filter, inspect and export the organization audit log, including restricted details, CSV exports, retention per plan and the audit API.
The audit log is the organization's security and change record. It lists who did what, to which record, from which surface and with what outcome. Events are append-only: nobody in the organization can edit or delete them.
The audit log lives under Organization, Account, Audit log in the sidebar. The routes are:
| Route | Purpose |
|---|---|
/{orgSlug}/audit-log | The event table with filters and exports. |
/{orgSlug}/audit-log/{eventId} | Event detail. |
Platform administrators have a separate log across organizations at Admin audit log. For how events are captured and stored, see Audit logs architecture.
Each event records:
Events are grouped into Authentication, Users, Permissions, Billing, Data, Settings, Integrations, Security and System.
Some events carry restricted request context: IP address, session ID and user agent. These fields are hidden by default. Revealing them requires a dedicated permission, and every reveal writes its own audit event.
Retention depends on the organization's plan:
| Plan | Retention |
|---|---|
| Starter | 1 day |
| Pro | 7 days |
| Business | 90 days |
| Enterprise | 365 days, or a custom period set by the platform |
A daily job removes events older than the retention period. See Billing and usage.
The table has columns for Timestamp, Actor, Event, Target and Source and outcome. Use Search events and targets to search, and the filters for date, actor kinds, event types, categories, sources and outcomes. Filters and paging live in the URL, so you can share a filtered view.
Select a row, or View details in its menu, to open the event detail page. It shows the event ID, actor, organization, local and UTC time, source, category, target, structured changes and request context. From there you can:
Select Exports in the table toolbar, then Create export. The export uses the current filters and needs a date range of no more than 90 days. Exports run in the background: refresh the panel to see Pending, Running, Completed, Failed or Expired. Download a completed export with Download export. Files expire after 24 hours.
Organization exports never include restricted details. Requesting, completing and downloading an export are audited.
| Key | Grants |
|---|---|
organization.audit-log.view | Open the audit log and event details. |
organization.audit-log.export | Create and download CSV exports. |
organization.audit-log.reveal | Reveal restricted details on an event. |
Opening an affected resource also requires the view permission of that record type, such as organization.customers.view or organization.tasks.view. See Access control.
The assistant side panel can summarize the visible results, explain a visible event and suggest filters.
MCP tools for the audit log:
| Tool | Kind |
|---|---|
listOrganizationAuditEvents | Read |
createOrganizationAuditExport | Write |
getOrganizationAuditExport | Read |
See MCP.
Paths are relative to /api/v1/organizations/{organizationId}.
| Resource | Operations |
|---|---|
audit-events | listOrganizationAuditEvents (GET) returns a cursor-capable page of redacted event summaries. |
audit-exports | createOrganizationAuditExport (POST) queues a CSV export of redacted events. |
audit-exports/{exportId} | getOrganizationAuditExport (GET) returns an export job owned by the caller, with a five-minute download URL while the file is available. |
audit-events requires organization.audit-log.view. Both export routes require organization.audit-log.export. Restricted details and sensitive metadata are never returned through the API. See API and OpenAPI.
Last updated on
Billing and usage
How an organization chooses a plan, pays through Stripe Checkout and the Stripe Customer Portal, and tracks metered usage, credits and limits on the Usage and Limits page.
Profile
How to manage your personal details, language, regional formats, theme, sign-in methods and notification channels, and which account pages live outside an organization.
