Audit log
The audit log is an append-only record of every administrative change made in your Hydra workspace. It's where you go to answer questions like "who deleted this channel?", "when did Alex become an Admin?", or "did anyone touch the 2FA policy last week?"
Every entry records who, when, what, and which target. Entries cannot be edited or deleted — the log is designed so that even an Owner cannot tamper with the history.
Where to find it
Team → Audit log (Admins and Owners only).
Members do not see the audit log in their sidebar and cannot access /team/audit-log directly.
What gets logged
| Area | Actions recorded |
|---|---|
| Team | Invite sent, role changed, teammate removed |
| Channels | Channel created, updated, deleted |
| Widgets | Widget configuration updates |
| Bots | Bot updates (persona, behaviors, directives, handoff config, etc.) |
| API keys | Key minted, key revoked |
| Policy | 2FA policy changed, plan changed |
| Flows | Flow published |
Read-only actions (viewing a conversation, opening a record, running a report) are not logged — this is an audit of mutations, not an access log. High-volume API traffic from external MCP clients has its own per-request log separate from this one.
Filters
Four filters combine with AND logic:
- Actor — limit to actions taken by one specific teammate.
- Action — limit to one type (e.g. "Minted API key").
- From / To — date range. Dates are inclusive on both ends.
Click Apply to run, Clear to reset.
Reading an entry
Each row shows:
- When — local time, converted from UTC.
- Who — display name + email of the teammate. "system" appears for entries without an actor (scheduled jobs, webhooks, etc.).
- Action — human-readable label, e.g. "Changed role".
- Target — the object type (
channel,bot,api_key, etc.) plus the first 8 characters of the target's ID for cross-reference. - Details — a small key/value block describing what changed. For updates, this is usually the list of changed fields; for invites it shows the email + role; for role changes it shows the before and after.
Retention
Audit entries are stored indefinitely in Hydra. There is no automatic purge, and no UI to bulk-delete.
Exporting
Bulk export is not yet available. If you need a specific range for compliance purposes, contact support and we can export directly from the database.
What the audit log is not
- Not a security-incident replay tool. Audit shows mutations at the application layer. Network-level attacks, credential theft, and direct DB access won't appear here.
- Not a message or conversation history. Conversations are stored in the Inbox with their own timestamps and reply authorship.
- Not a flow execution log. Flows have their own run history under Flows → Runs.