Audit Log
Review security audit log entries, retention, and search.
The audit log is a tamper-evident record of security-relevant activity in your organization. Organization admins use it to answer who changed what, when an API key was created, or which admin updated SSO settings.
Logging is always on and cannot be disabled. The sections below cover access, what is recorded, search and filtering, retention, and export.
Accessing the audit log
The audit log gives org admins a complete, tamper-proof record of security-relevant activity inside their StatusDashboard organization. It is designed to help you answer questions like:
- Who invited this user, and when?
- Which admin changed our SSO configuration yesterday?
- When was our API key created, and by whom?
Only org admins can view the audit log — team members without the admin role will see an access-restricted message.
What is recorded
StatusDashboard records audit events for essentially all meaningful activity in your organization. Logging is always on — you do not need to configure anything, and it cannot be disabled.
Each entry captures who performed an action, what happened, when it occurred, and (when applicable) which resource was affected. That includes changes made by team members in the admin console, actions taken through the API or webhooks, automated background processes, and support actions performed by StatusDashboard staff.
The Action column in the audit log shows a plain-language description of each event. Browse your organization's history to see the full set of recorded activity for any date range.
Events with no human initiator — such as billing renewals, scheduled jobs, or other automated processes — are shown with a System badge rather than an individual user's email.
How to search
The audit log requires you to set a date range before results are returned.
Filters available:
- From / To — the date range to search (both inclusive). Defaults to the last 7 days.
- Actor email — optionally narrow results to events performed by a specific user.
Click Search to load matching events. Results are shown in a paginated table — 10 events per page — with Prev and Next controls at the bottom of the list. Use the refresh button to reload the current page after filters change.
The dashboard does not include CSV export. Use Prev / Next (or the API with nextToken) to browse additional pages within your retention window.
Event details
Each event row shows:
| Column | Description |
|---|---|
| Timestamp | The date and time the event occurred (your local timezone) |
| Actor | The email address of the user who performed the action, plus a type badge. Platform staff actions show a StatusDashboard Staff badge with no email address. |
| Action | A human-readable description of what happened |
| Resource | The specific item affected, shown as a color-coded type badge and an identifier. For example, an "Invited user" event shows a green User badge next to the invited email address; a "Plan changed" event shows a gray Account badge. |
Actor type badges
| Badge | Meaning |
|---|---|
| User | A human team member who signed in with email/password or SSO |
| API Key | An automated integration using a StatusDashboard API key |
| System | An automated background process with no human initiator (e.g. a billing renewal or trial expiry) |
| StatusDashboard Staff | A StatusDashboard platform administrator performing a support action. The staff member's email is not shown to tenants. |
Event retention
Audit logging is always on for every organization — you cannot disable it, and there is no separate plan feature to enable it.
How long events are kept is controlled by the auditRetentionDays plan limit. Every org has this value (minimum 1 day). It sets automatic expiry for stored events — it does not gate access to the audit log UI or this API. Longer retention is included on higher tiers; see Billing. Platform administrators can adjust retention per org (1–9999 days).
When an event reaches the end of its retention period, it is removed automatically. StatusDashboard does not provide a way to manually delete audit events before that expiry; this is intentional to ensure the log is non-repudiable.
Immutability
Audit events are append-only. Once an event is written it cannot be modified or deleted through the API or the dashboard. This design ensures the log is suitable for compliance purposes.
Notes for enterprise and compliance use
- Events triggered via API key are labeled with the key owner's email and an
API Keybadge so automated actions are distinguishable from human actions. - Audit browsing is paginated (default 10, max 100 per request) and is not intended for bulk export.
- For SOC 2, HIPAA, or similar compliance requirements, reach out to support to discuss extended retention or SIEM integration options.