Audit logging allows administrators to track changes across their TestRail instance. With auditing enabled, and the audit level set to High, every entity that’s created, updated, or deleted is recorded. This provides a full trail of activity for compliance, accountability, and troubleshooting.
Audit Logging is an Enterprise-only feature. Contact us if you need to upgrade your license to the Enterprise tier.
Enabling and configuring auditing
You can configure audit logging from the administration console:
Go to Admin > Site Settings > Auditing.
-
Choose an Audit Level:
Low – Minimal logging
Medium – Standard logging
High – Full tracking of all entities created, updated, or deleted
Save your changes.
Configuring Audit Log storage
On the Auditing > Configuration tab, administrators can adjust how many records are displayed and stored:
Number of Rows – Adjusts how many records appear on the log page.
Maximum Number of Audit Records Stored – Defines storage limits for records.
Maximum Number of Days to Store Records – Defines retention period.
👉 For TestRail Server installations, make sure the background task is enabled so that audit data is purged according to the defined retention policy.
Additional options for Server Administrators
If you’re running TestRail Server, you have extra flexibility:
External Logs – Logs can be written to an external location and viewed using your preferred log reader.
Configuration requirements for upgrades
If you are upgrading your TestRail Server installation (not a fresh install), you need to:
Create an audit folder for your installation.
Set the correct permissions so TestRail can write to this folder.
Add the folder path to your
config.phpfile by including the following line:
define('AUDIT_PATH', '<filepath>');Using the audit log
Once auditing is switched on, you can monitor CrUD changes (Create, Update, Delete) across the entities in your TestRail instance, by navigating to the Auditing > Log tab.
On the Log tab, depending on your auditing level, you’ll see the following changes are recorded to the log:
| Auditing level | Changes recorded |
|---|---|
| High | Updates, deletions, creations |
| Medium | Updates, deletions |
| Low | Deletions only |
You can configure the level of logging depending on the requirements of your team. Each row of the log contains the following information:
| Column level | Column description |
|---|---|
| Date | Date and time which changes were made |
| Entity Type | The TestRail entity that was changed |
| Entity ID | The ID of the entitiy that was changed |
| Entity name | The defined name of the entity that was changed |
| Action | The type of change – Change, Delete, or Create |
| Author | The username of the user who made the change |
| Mode | The mechanism which the change was made – UI or API |
With logging activated and with some audit logs generated, you can filter for specific events using the Log filter. And if you wish to export the log for more detailed analysis, you can do so using the Export button.
The Forget User functionality will also obfuscate the user details in the audit log within TestRail.
AI-specific auditing
When generating test cases with AI, administrators may want visibility into how AI is being used within their TestRail instance. Audit logging now extends to the following AI actions:
Create AI - Logged when a new test case is generated by AI.
Update AI - Logged when an AI-generated test case is edited by the user.
Delete AI - Logged when an AI-generated test case is deleted.
These entries allow administrators to trace the lifecycle of AI-generated content and ensure compliance with internal standards or external regulatory requirements.