View the Audit Log

How owners and admins review, verify, and export the tamper-evident audit log for important company activity.

Written by Maya ThompsonUpdated 6 days ago3 min readBeginner

What this guide covers

This guide explains how to use the audit log to review security-sensitive company activity. The tamper-evident audit trail focuses on money, permission, data-access, and export events so owners and admins can investigate important changes.

Before you begin

You need Owner or Admin permissions to access the audit log.
Audit export and chain verification are available to company owners and admins.

Step 1: Open the audit log

Go to Settings.
Open Audit Log in the owner-only settings section.
Review the summary cards for the filtered event count, last sequence, chain status, and next export cursor.

Step 2: Read log entries

Each entry records:

Sequence -- the event's position in the company audit chain.
Timestamp -- when the event occurred.
Category and action -- the audit category plus the stable action name, such as a money, permission, data-access, or export action.
Actor and target -- the team member id and affected record id when they are available.
Request details -- method, route, and response status.
Hash link -- the previous hash and stored event hash used for verification.

Step 3: Filter the log

Use the filter controls to narrow results, then select Apply filters:

Category -- money, permission, data access, or export.
Environment -- live or sandbox.
Exact action -- a specific stable action name, such as money.post.invoices.id.send.

If more events match the filters, use Load more to continue through the sequence cursor.

Step 4: Verify the chain

Select Verify chain to recompute the audit hash chain for your company. When verification returns VALID, the stored sequence, previous-hash links, and event hashes are intact. If verification fails, contact support and include the broken index shown on the page.

Step 5: Investigate suspicious activity

Look for:

Mass deletions of records.
Settings changes by unexpected users.
Role changes or new team member invitations.
Unexpected exports or repeated money workflow changes.

Step 6: Export the log

Select Export JSON to download the filtered tenant audit manifest. Use exports for:

Compliance audits (SOC 2, GDPR).
Internal security investigations.
Management reporting.

If the export includes a nextCursor, load or export the next page before treating the file set as complete.

What actions are logged

Money actions such as quote, invoice, payment, and billing changes.
Permission actions such as team and user administration.
Data-access mutations across core workspace records.
Tenant data exports.

Note: Tenant audit entries are hash-chained so edits, deletions, or reordering can be detected during verification. Coverage is expanding; the current trail should not be treated as a record of every possible company action.

Did this answer your question?