Audit Logs
Audit Logs give admins a tamper-evident record of every significant action across the workspace.
Accessing Audit Logs
Go to Admin Panel → Audit Logs. The log table loads automatically with the most recent activity first. No configuration is required, logging begins as soon as your workspace is active and can’t be disabled.
What gets logged
Audit Logs capture a broad range of events across four categories.
Documentation events:
- Publishing a documentation
- Creating a documentation
- Deleting a documentation
- Documentation-specific settings and configuration updates
Branding and developer portal events:
- Applying or switching a branding template (Solid, Bloom, Roboto)
- Saving changes to colors, custom CSS, or custom JavaScript
- Reverting to a previous branding version
- Updating custom domain configuration
Workspace and membership events:
- Inviting a new member to the workspace
- Changing a member's role (e.g. Editor → Admin)
- Removing a member from the workspace
- Member login and logout events
- SSO configuration changes
Admin-specific events:
- Modifying workspace-level settings
Log entry structure
Every entry contains the following fields.
- Member — who performed the action (e.g. Jane Smith, jane@company.com)
- Action — what happened (e.g. “Published documentation project”)
- Timestamp — date and time, in the viewer’s local timezone
- IP address — where the action came from
Using Audit Logs for compliance
Audit Logs support internal security reviews, compliance reporting, and incident investigation.
1
Identify the event or timeframe
Open Admin Panel → Audit Logs.
2
Filter by member or event type
Use the member filter to isolate a specific account, or the event-type filter to focus on a category, such as all branding changes or all publish actions across any time range.
On this page
- Audit Logs