Audit Logs
How admins review, filter, and export audit history for compliance and operational oversight.
What the audit log is
The audit log records important activity across an organization. It gives admins a searchable history of operational changes, who made them, and when they happened.
Audit logging is designed for accountability and compliance. It helps teams review configuration changes, investigate unexpected updates, and produce a record of activity when required.
What is logged
Navis Docs records lifecycle events for the main objects that shape an organization and its knowledge base.
- Departments and teams
- Procedures, procedure versions, categories, and rollouts
- Users, invitations, and role changes
- Organization settings and billing-related management actions
- News posts and related team announcements
- Audit export requests and export completion events
Where relevant, events include before and after JSON snapshots. These snapshots make it easier to understand exactly what changed, not just that a change occurred.
Where to find it
Admins can open the Audit Log page from the main navigation. Members do not see the audit log navigation item and cannot access audit records.
Because the log can include sensitive operational history, keep audit log access limited to users who need organization management or compliance responsibilities.
Filtering events
The Audit Log page includes filters so admins can narrow the history to the records they need.
- Entity type: focus on areas such as procedures, users, departments, teams, news, or rollouts
- Actor: review activity performed by a specific user
- Date range: limit results to the time window relevant to an investigation or review
Combining filters is useful during investigations. For example, an admin can filter to procedure events performed by one actor during the week a policy changed.
Exporting audit records
Admins can request an audit export when they need an offline record or a file for compliance review. Exports are generated asynchronously so large requests do not block normal app usage.
The export job moves through these statuses:
QUEUEDPROCESSINGREADY
When the export is ready, Navis Docs provides a signed download URL for the generated JSON file. Export activity is itself audited with events such as AUDIT_EXPORT_REQUESTED and AUDIT_EXPORT_READY.
Access control
The audit log is admin-only. Owners and admins can review records and request exports. Members cannot access the page, run filters, or download export files.
Treat exports with the same care as the in-app audit log. Downloaded JSON files may contain sensitive information about users, organization configuration, and operational changes.
Suggested review workflow
1. Start with the question
Decide what you are trying to understand, such as who changed a procedure, when an invitation was sent, or how a department was restructured.
2. Apply focused filters
Filter by entity type, actor, and date range to reduce noise. Start narrow, then widen the filters if the expected event does not appear.
3. Review before and after data
For events with snapshots, compare the before and after JSON to understand the actual change. This is especially useful for procedure, role, and settings updates.
4. Export when a record is needed
Request an export when you need to share or archive audit history. Wait for the job to reach READY, then use the signed URL to download the JSON file.