Search help articles
theme_search
Administration & Settings

Audit Log

Last updated

The audit log is a read-only record of what happened in your company account and who did it. Each row is one event: when it happened, which member performed it, what kind of data it touched, what was done, and the IP address and device the request came from. Where an event changed stored values, the row also carries a before-and-after comparison of each field.

Use it to answer questions after the fact. Who approved this leave request, and when? Who edited a time entry two weeks after it was logged? When did this role gain permission to view wages?

You can also reach the log from a single record: the Change history button on the leave request popup and the time entry view popup opens this page pre-filtered to that record. It appears only for users who can change company settings.

Trackabi records these events continuously in the background. Nothing on this page changes your data.

Before you start

The Audit log tab is available on every plan. What differs is how far back it reaches: events are recorded continuously whatever your subscription, and the plan determines how much of that history you can view.

On plans with the shortest window, the page shows the last 24 hours of events, followed by a banner reading You're seeing only the last 24 hours and an Upgrade Plan button that opens Settings > Subscription, where the retention included in your plan is shown. Rows below the visible window are shown greyed out as a preview and cannot be read.

Interface at a glance

Filter the log to narrow down what you are looking for, then read the events below. Each row is one event, newest first, and more load as you scroll.

The log is append-only. You cannot edit or delete an entry, and there is no export.

Filters and search

Filter the log by Date, Member, Data type, Action type, or Keyword, and reset the whole row with the button at its right-hand end. The filters combine, so setting more than one narrows the result to events matching every condition. Date starts on the current month rather than showing everything.

To trace one record, type ID: followed by its numeric id in Keyword. That returns the events for exactly that record and nothing else. The match is exact, so ID:12 does not also return ID:123. Without the prefix, Keyword searches the text recorded with each event, including the IP address, the device string, field labels, and the values on both sides of a change.

To narrow by what was done, pick a Data type first. Action type then offers only the actions that type can carry, which is usually the shorter and more useful list. Choose Leave, for example, and Action type offers Created, Deleted, Leave approved, Leave canceled, Leave rejected, and Updated. Changing Data type clears any action already chosen.

Two limits are worth knowing before you rely on a filter. Clearing the date with the × removes your own date restriction but not the plan's retention window, so the log still reaches back only as far as your subscription allows. And Data type and Action type show only their first 14 options; see Notes and behavior below.

The event table

Each row records when an event happened, who performed it, what it affected, and what changed. Hover any truncated value to see it in full.

Times are shown in your own time zone, not the time zone of the person who performed the action.

Most columns say what they hold. Three are worth a word:

Data type identifies settings pages by their location, for example Organization Settings / Leave types, so a change is traceable to the screen it was made on.

Client Related Data is the device or application behind the request. Web sessions show the browser's user agent, the desktop app appears as a trackabi.timer/… string, and the mobile app shows a readable device summary naming the app version, operating system, and model.

Changed data is the before-and-after of the fields the event touched. Role and permission changes appear here under the Role data type. For details on what those permissions do, see User Access Roles & Permissions.

Reading the Changed data column

It renders in one of three ways, depending on the event.

Nothing. Session events of data type Authentication carry no field changes and leave the cell empty.

A single line of text. Where an event changed exactly one value, it is written inline, as in email: user@example.com on a successful sign-in.

A magnifier icon. Where there is more to show, the cell holds an icon; hover it for the detail. The tooltip has up to four parts:

  • a summary line identifying the record, for example Leave for [member name] — Vacation (ID: 12345)
  • a secondary line with the date the record refers to, for example Aug 21, 2026
  • one line per changed field, as Field: old → new
  • a closing note reading Added via public API on events that came in through the API rather than the interface

Empty values read as (none), so a field being filled in for the first time appears as Approved By: (none) → [approver name]. Color values are shown with a swatch next to the hex code. Bulk timesheet imports and exports list a sample of the affected entries, ending in … where more exist than the sample shows.

Notes and behavior

Some filter options are not in the list. Data type and Action type each show only their first 14 options alphabetically, so Project, Report, Role, Sign in, Task, Team, and Timesheet are not among the data types you can pick, and actions such as Updated, Sign-in failed, and Role permissions changed are missing from the unfiltered action list. Events of all these types still appear in the table.

To reach them, pick a Data type first. That shortens the Action type list enough for all of its options to fit, including ones absent from the unfiltered list. For the seven data types you cannot pick, search with Keyword instead. Member is unaffected, because it filters as you type.

Names are historical, avatars are live. The name on a row is the one captured when the event was written, so a row keeps showing the correct person after they are renamed or removed from the company. The avatar is drawn from the member's current profile where they are still in the company, and falls back to initials otherwise. Rows with no member context, such as a failed sign-in, may show no name.

Rows load as you scroll. The table requests 50 events at a time and appends the next batch as you approach the bottom.

Sorting and column layout are fixed. Columns cannot be sorted, reordered, resized, or hidden, and the sort is always newest first.

The empty state. With no matching events the table is replaced by an icon and the message No audit events match the current filter. Widen the date range or clear a filter, and remember that the plan's retention window still applies.

theme_flash_true