Skip to main content
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, compliance and audit: who uses Triggr, a locked compliance log written by a workflow, and the audit log (1:26).

​
Adoption

Tools > Adoption is for organisation admins only.
The Adoption page with CSV and Refresh buttons, filters for Last 30 days, a time zone, All, Studio or Core, and Days or Weeks, and tiles for People active 15 of 17, Sessions 320, Active time 11h 9m and Median session 34s.
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.
The Who is using Triggr heatmap with a Search people box and Least active first sort, two people under No activity in this period and three under Active, with a darker square on days each person used Triggr.
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.
1

Start the log

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.
The Start Compliance Log step panel with Name set to Leaver – followed by the leaverName parameter.
2

Add an entry after each action

Add Compliance Log Entry with a Title and Detailed Description; both accept variables.
A workflow running Manual Trigger, Start Compliance Log, three Compliance Log Entry steps named Sign-in blocked, Licences removed and Mailbox converted, and Lock Compliance Log, with the Sign-in blocked panel showing a Title and a Detailed Description that includes the leaverEmail parameter.
3

Lock it

End with Lock Compliance Log. It adds a final Compliance Log Locked entry and refuses further entries.
4

Read or export it

Go to Compliance > Compliance Logs, search by name or filter by client, and click View. Export PDF downloads the log.
The Compliance page with a Search logs box, an All Clients filter, and one locked log, Leaver – Jane Doe, with No Client, a created date and a View button.
A locked compliance log named Leaver – Jane Doe with an Export PDF button, Created At, Last Updated and Entries 4 total, and entries for Sign-in blocked, Licences removed, Mailbox converted and Compliance Log Locked with their times and descriptions.
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 Audit Logs page filtered by a workflow ID, with All Methods, All Services and date filters, and an expanded PUT row by Alex Morgan showing User ID, Service workflows, Endpoint UpdateWorkflow, IP Address and the request and response bodies.
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.

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