Owlat Docs

Audit Logs

A chronological record of significant actions in your Owlat organization, so you can see who did what and when.

Audit logs provide a chronological record of significant actions taken in your Owlat organization. They help you answer "who did what, and when" — essential for security reviews, compliance, and debugging unexpected changes.

Viewing audit logs

Open Settings > Technical > Audit Log to browse your organization's activity history. Each log entry includes:

  • When — the timestamp of the action
  • Who — which team member performed it
  • What — a description of the action taken
  • Details — additional context about what was changed
Admins only

The audit log is restricted to organization owners and admins. Editors do not have access — they see an "Admins only" gate instead of the log.

Use the search box to filter entries by user, action, or details, and narrow the view with the dropdown filters: by resource type, by team member, and by date range (Last 24 Hours, Last 7 Days, Last 30 Days, or All Time). Stats cards at the top summarize total actions plus breakdowns for campaigns, contacts, and settings over the selected range. Note that the "All Time" option summarizes only roughly the last 90 days of activity in the stat cards, while the log list below shows the full history.

Tracked actions

Audit logs capture actions across your organization, including:

  • Team changes — members invited, roles changed, members removed
  • Campaign activity — campaigns created, sent, scheduled, cancelled, flagged for review, and A/B test lifecycle
  • Content changes — email templates, transactional emails, and saved blocks created, updated, published, or deleted
  • Audience changes — contacts imported, topics created or modified, segments created/updated/deleted
  • Automations — automations created, activated, paused, and resumed
  • Settings changes — API keys created or revoked, webhook endpoints added or removed, sending-domain lifecycle (registered, verified, regenerated, deleted)
  • Blocklist — entries added or removed
  • Inbound & agent activity — Postbox draft and outbound transitions, inbound message handling, and AI-agent configuration changes
  • Abuse status — changes to your organization's sending abuse status

Common use cases

Security review

When investigating a potential security concern, use audit logs to:

  • Check if any API keys were created or revoked unexpectedly
  • Verify who made recent settings changes
  • Review team membership changes

Compliance

For organizations with regulatory requirements, audit logs provide the paper trail you need:

  • Demonstrate that access controls are being enforced
  • Show when and by whom data was modified
  • Track consent-related changes

Debugging

When something unexpected happens — a campaign was sent to the wrong topic, a template was modified, or a setting was changed — audit logs help you trace back to the specific action and person.

Make it a habit to check audit logs after any unexpected behavior. They often reveal the cause faster than investigating the symptoms.

Best practices

  • Review regularly — don't wait for an incident. Periodic reviews help you spot unusual patterns early.
  • Correlate with team changes — when someone joins or leaves, review audit logs to verify that access changes were handled correctly.
  • Use for onboarding — show new admins the audit log so they understand the accountability model.

Next steps

Next Share Links