Atteny

The audit log

Who changed what, and when — the record behind sensitive settings and approvals.

For admins
Updated July 26, 2026

Whenever someone changes something that matters — approves a timesheet, edits a pay rate, moves a person between locations, changes a company setting — Atteny writes a line to the audit log. It's the record you reach for when you need to know who did what, and when.

Only administrators can open the audit log. Settings is admin-only, and the server returns nothing at all to a manager or employee — typing the URL directly gets them an empty page, not the data.
  1. 1

    Open the audit log

    Go to Settings → Audit Log. Entries are listed newest first, and the badge beside the title tells you how many are loaded.

    The Audit Log settings page with the action and entity filters and a list of recent entries
  2. 2

    Read a row

    Each row shows four things: Action (what happened, as a coloured label), User (who did it), Entity Type (what kind of record it touched), and Timestamp in your company's date and time format.

  3. 3

    Narrow it down

    Two dropdowns sit above the list — All actions and All entities. Both are built from what has actually happened in your account, so you only ever see options that exist. There is no date or person filter.

  4. 4

    Open an entry for the detail

    Rows that carry a before-and-after snapshot have a chevron on the right. Select the row to expand it and you'll see the Entity ID plus Previous Values and New Values — the exact fields that changed. Rows without a snapshot (a delete, an approval) don't expand.

    An expanded audit log row showing Entity ID with the Previous Values and New Values panels side by side

What gets recorded

AreaExamples
People and accessEmployee updated, employment details updated, locations set, onboarding completed, device cleared, employee deleted
InvitationsCreated, re-sent, cancelled, accepted
TimesheetsApproved, rejected, created manually, edited, deleted, clock-in or check-out verified, clocked in on behalf of someone
Overtime and TOILOvertime approved, rejected or unapproved; TOIL accrued, requested, approved, rejected
LeaveRequests approved, rejected or cancelled; leave rules and balance overrides
SchedulingShifts created, updated or deleted; auto-schedule applied; open shifts claimed or released; shift swaps
PayPay rates created, updated or deleted; payroll config and payroll runs
Company setupOrganisation details, settings, modules, locations and location settings, areas, NFC tags, employment types
ReportsReport exported; scheduled reports created, updated or deleted
AccountCompany created; account deletion requested and completed
Routine clock-ins and clock-outs are not in the audit log — they live on the timesheet itself, in Time clock records. The audit log only picks up clocking when something unusual happens: a GPS check bypassed pending approval, a device blocked or warned by policy, or an admin clocking someone in on their behalf. Reading or viewing data isn't recorded either, apart from report exports.

How far back it goes

The page loads the 200 most recent entries — filtered first if you've picked an action or entity, so a filter reaches further back than the unfiltered list. Older entries stay in your account; they're simply not served to this page, and nothing deletes them on a schedule. The audit log is available on every plan.

The audit log records changes, not intent. It's most useful alongside Editing timesheets — a deleted timesheet leaves an audit line behind even though the entry itself is gone — and Roles and permissions, which tells you who was able to make the change in the first place.

Related articles

Still need help?

Contact support