Audit Trail and Compliance
Understand what Transform records, how to review it, and how it supports compliance.
Overview
Audit trail records who changed what, and when.
Use it for compliance, investigations, and stakeholder confidence.
Key Concepts
Audit event: recorded change, such as a status update
Actor: Teammate or system process that performed the change
Retention: how long audit data remains available (plan dependent)
How It’s Used
Use audit trail during approval reviews and investigations.
Use it to establish accountability for scope and status changes.
Benefits
Clear accountability for high-impact changes
Stronger governance evidence for approvals
Faster root-cause investigation during delivery issues
Setup Steps
Account configuration varies, but audit events often include:
status changes
ownership/assignee changes
field edits (priority, due date, tags)
link changes (requirements ↔ tasks ↔ tests)
comments and mentions
Best Practices
Record approvals in comments using a consistent pattern.
Validate high-impact changes using source links and audit events.
Confirm retention and exports during governance design.
For formal compliance requirements, confirm retention and export settings with an Account Admin.
Troubleshooting
Summary
Audit trail provides the evidence layer for governance and compliance.
Related:
Last updated

