> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Adoption, compliance and audit logs
> See who in your team uses Triggr, keep a locked record of what a workflow did for a client, and review the requests made in Studio and Core.
Tools > Adoption shows who in your team uses Triggr, Compliance > Compliance Logs holds the locked records your workflows write, and Compliance > Audit Logs lists the requests your team makes in Studio and Core.
## Adoption
Tools > Adoption is for organisation admins only.
Who is using Triggr lists everyone in your organisation, including people who have Never used Triggr; click a name to see what they worked on and the forms they submitted. CSV downloads the list.
Active time counts only while a Triggr tab is visible and in use; a session goes idle after two minutes without input. Triggr keeps page views for 90 days and sessions for two years.
## Compliance logs
A compliance log is a named, timestamped record of what a workflow did, such as every step of a leaver for a client. Once locked, nobody can change or delete it.
Add **Start Compliance Log** (Compliance) near the start of the workflow and give it a Name. The log belongs to the run's client, if it has one.
Add **Compliance Log Entry** with a Title and Detailed Description; both accept variables.
End with **Lock Compliance Log**. It adds a final Compliance Log Locked entry and refuses further entries.
Go to **Compliance > Compliance Logs**, search by name or filter by client, and click **View**. Export PDF downloads the log.
To add to a log from a later run or another workflow, pass its ID (the Start Compliance Log step's `compliance_log_id` output) to **Set Compliance Log** before the entries. Everyone in your organisation can view and export compliance logs, and Triggr keeps them indefinitely.
## Audit logs
Compliance > Audit Logs lists the requests signed-in people make in Studio and Core, including page loads. It appears in the menu for admins and anyone with View Audit Logs.
The list shows the newest 50 matching requests, so filter by path, method, service or date to find older ones. Click a row for who made it, from which IP address, and the request and response bodies. Fields named `password`, `secret`, `token`, `key` and similar show as `[REDACTED]`; anything else is stored as sent, including the settings you save for an integration. Bodies over 16 KB aren't stored. Triggr keeps full entries for 30 days, then the entry without its bodies until 400 days. Workflow runs aren't requests by a person: find them on Executions.
## GDAP alerts
Settings > GDAP Alerts is the same digest as Triggr Core's Settings > Alerts; a change in either app applies to both. See [GDAP alerts](/core/manage/gdap-alerts).
## FAQ
Ask an admin to open Tools > Adoption, or to export the CSV for you.
Older activity was rebuilt from audit logs rather than measured in the browser, so it shows as inferred or not measured.
A Compliance Log Entry or Lock Compliance Log step ran before Start Compliance Log or Set Compliance Log. Move the start step earlier on every path.
The log was locked earlier in the run. Put **Lock Compliance Log** last.
The run had no client when Start Compliance Log ran. Set the client first, for example with **Set Client By ID**.
No. Copy a request or response body with the copy button on an expanded row.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.