Audit Log

The audit log is a tamper-evident record of important actions taken in your team. It's the first place to look when you need to answer "who changed this, and when?" -- whether you're investigating an unexpected configuration change, reviewing security activity, or satisfying a compliance requirement.

You'll find it under Settings > Audit Log in the dashboard.

What Gets Recorded

The audit log captures meaningful, security- and configuration-relevant actions, including:

• Authentication & security -- SSO logins, password changes, email changes, enabling or disabling two-factor authentication, regenerating recovery codes, registering or removing passkeys, and signing out sessions.
• Team members -- invitations sent, resent, or revoked; members removed; role changes.
• API tokens -- tokens created and revoked.
• Account & team settings -- profile updates, branding changes, security-policy changes, SSO configuration changes, custom-email (SMTP) changes, and notification-preference changes.
• Monitoring operations -- checks enabled, disabled, snoozed, or manually run.
• Incidents -- incidents acknowledged, snoozed, archived, or restored.
• Status pages -- status-page updates created, edited, or deleted.

Each entry records what happened, who did it, the time it happened, and -- where relevant -- the before-and-after values of what changed. Sensitive values such as passwords and client secrets are redacted and never stored in the log.

Who Can View It

Viewing the audit log requires the Settings read permission, so it's available to admins (and to any integration whose API token has the settings:read scope). As with all data in Hoppla, the log only ever shows activity from your own team.

Filtering

The audit log can grow quickly, so the view gives you a few ways to narrow it down:

• Filter by action -- show only a specific type of event (e.g. only role changes, or only token creations).
• Filter by entity type -- focus on a kind of resource, such as monitors, checks, incidents, status pages, team members, or API tokens.
• Browse chronologically -- entries are listed newest-first, and you can page back through the history.

Click any entry to expand it and see the full details, including the exact fields that changed.