Owlat Docs

Audit Logs

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

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 > Audit 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

Tracked actions

Audit logs capture actions across your organization, including:

  • Team changes — members invited, roles changed, members removed
  • Campaign activity — campaigns created, sent, cancelled
  • Settings changes — API keys created or revoked, webhook endpoints added or removed, domain changes
  • Content changes — templates created, updated, or deleted
  • Audience changes — contacts imported, lists created, segments modified

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 list, 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 Email Editor