Product documentationUpdated October 3, 2025
Audit Logs
Audit logs capture who did what, when, and from where—filter and export events to support investigations, compliance, and operational oversight.
Overview
Audit logs provide a record of user actions and system events. They are the primary tool for answering:
- Who changed something?
- What changed?
- When did it happen?
- Where did it originate (IP/device)?
What audit logs typically include
- timestamp
- user and role
- action (create/update/delete/execute/configure)
- entity (project, endpoint, test, system setting)
- status (success/failure)
- source IP or origin
Filtering and investigation workflow
- Filter by time range first.
- Narrow by user/role.
- Filter by entity and action.
- Export results for compliance or incident response.
Best practices
- Review audit logs regularly (weekly/monthly depending on your security posture).
- Keep admin access limited and monitored.
- Pair audit logs with Debug logging for troubleshooting (enable debug temporarily).
Related articles
Related articles
- AI Settings · Product documentation
- Configuration · Product documentation
- Debug Logging · Product documentation
- Email Settings · Product documentation
- Email Templates · Product documentation
- License Management · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.