> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/audit-trail-and-compliance.md).

# Audit Trail and Compliance

### Overview

Audit trail records who changed what, and when.

Use it for compliance, investigations, and stakeholder confidence.

{% hint style="info" %}
Screenshot placeholder: audit trail view showing field changes with timestamps.
{% endhint %}

### 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

{% stepper %}
{% step %}

### Open the item to audit

Open the requirement, task, test case, project, or artifact.
{% endstep %}

{% step %}

### Open Audit Trail / History

Look for a tab or panel labeled **Audit trail**, **History**, or **Activity**.
{% endstep %}

{% step %}

### Capture evidence

When sharing findings:

* copy a permalink to the item
* capture a screenshot of the relevant event(s)
* add a summary comment with `Decision:` and `Approved by:` when applicable
  {% endstep %}
  {% endstepper %}

### 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.

{% hint style="warning" %}
For formal compliance requirements, confirm retention and export settings with an Account Admin.
{% endhint %}

### Troubleshooting

<details>

<summary>I can’t see audit trail data</summary>

Possible causes:

* insufficient permissions
* audit trail feature is not enabled

Ask an Account Admin to confirm access and configuration.

</details>

<details>

<summary>I need account-wide logs</summary>

Item-level history may not cover account-level actions.

For Organization-wide reporting, review Account configuration or contact support.

</details>

### Summary

Audit trail provides the evidence layer for governance and compliance.

Related:

* [Tracking Changes and Decisions](/collaboration-and-automation/tracking-changes-and-decisions.md)
* [Comments and History](/collaboration-and-automation/comments-and-history.md)
* [Notification Settings](/collaboration-and-automation/notification-settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/collaboration-and-automation/audit-trail-and-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.