When a note looks wrong or a time entry doesn't add up, you don't have to guess how it got that way. The audit log records system activity, so you can see exactly what happened and when. This guide shows you how to use it to trace an error back to its source.

What the audit log is

The audit log is an admin-only record of activity across Enmantle, scoped to your agency — as the page itself puts it, "a full, tenant-scoped record of who did what. Sign-ins, content changes, and administrative actions." It lives under Tenant Settings on the Audit Log tab, and only Super-Admins can open it. It's not a report you hand to staff — it's the behind-the-scenes trail you use when you need to understand how a record reached its current state. Because it's admin-only, staff can't see or edit it, which is what makes it trustworthy for review.

What each entry shows

The audit log is a timeline, not a spreadsheet. Each entry tells you, in one line:

Who — the person's name and email (or Unknown user if it can't be resolved).
What — a plain-language action tagged with a category pill: Sign-in, Created, Changed, or Removed.
What it touched — the record the action was tied to, shown as an underlined target.
When — a relative time like "2 min ago"; hover for the exact timestamp.
From where — the IP address, when one was captured.

Trace a documentation or time-entry error

When a daily note reads wrong or a shift's time looks off, work backward from the record to the activity behind it.

Go to Tenant Settings → Audit Log.
Narrow to the record in question with the search box and filters (see below) — the resource, the kind of change, or the time window where the problem shows up.
Read the entries in order. The sequence tells the story: when the record was created, and any changes after.
Confirm what you're seeing, then go fix the underlying record.

Once you've found the bad entry, correct it the normal way. For a time entry, that's a time-entry change request — see Fixing a time entry. Every correction is itself recorded, so the trail stays complete.

The audit log tells you what happened. It doesn't change the record — you still make the fix in the right place. Think of it as your read-only source of truth for "how did this get here?"

Filter down to what you need

Three controls narrow the log to the entries that matter:

Search — the Search actions, resources, or IDs… box matches an action, a resource type, or a specific record ID.
Kind — filter by category: All events, Sign-in, Created, Changed, or Removed.
Within — limit the time window to 24 hours, 7 days, 30 days, or All time.

The log is read-only and stays in the app — there's no export or download control today, so review it in place and capture what you need for your records.

When to reach for the audit log

A daily note or score doesn't match what you expected.
A time entry was changed and you want to know by whom and when.
You're preparing for a review and want a clean record of activity.

For routine summaries you check on a cadence, build a saved report instead — see Build a custom report and schedule it to your inbox.

Next steps

Correct a bad time record with a time-entry change request.
Reviewing incidents alongside the trail? See Reviewing and filing UIs and MUIs.