Skip to main content
Audit logs record security-sensitive actions performed within your Cal.com organization. Each event captures who performed the action, what changed, and when it happened. Use audit logs to monitor access control changes, investigate security incidents, and satisfy compliance requirements.
Audit logs are an enterprise feature available to organizations on Cal.com. Events are recorded automatically — no configuration is required.

Tracked events

Cal.com automatically records audit events across the following categories: security, access control, API credential lifecycle, workflow automation, billing, and event type management.

Security events

Access control events

These events are recorded when organization or team memberships change.

API credential events

Workflow events

Billing events

These events are recorded when subscription or seat changes occur.

Event type events

Event structure

Each audit event captures a consistent set of fields:
IP addresses are stored as HMAC hashes for privacy. Raw IP addresses are never persisted in audit logs.

Access control event examples

Role change

When an admin changes a team member’s role, the audit log captures both the previous and new role values:
  • Action: ROLE_CHANGED
  • Target type: membership
  • Previous value: MEMBER
  • New value: ADMIN

Member removal

When members are removed from a team, an audit event is recorded for each member and team combination:
  • Action: MEMBER_REMOVED
  • Target type: membership
  • Target ID: The affected member’s ID

Member invitation

When new members are invited, the audit log records the invitation details:
  • Action: MEMBER_ADDED
  • Target type: membership

PBAC permissions for audit logs

If your organization uses PBAC (Permission-Based Access Control), audit log access is governed by dedicated permissions: Assign these permissions to custom roles to control who can access audit log data.