HomeHelpAdministrationAudit Trails

Audit Trails

Read the Audit Logs screen, filter it, export it, and understand what retention and purging mean for your records.

Super AdminOrg AdminConsultant AdminAccountantLast reviewed 29 Oct 2026

Was this article helpful?

Related Articles

User Management

The Super Admin screen at Admin > Users > User Management: creating users, editing, password resets, deactivating versus archiving, and bulk activate/deactivate.

Role Assignment

What each of the eight roles can reach, why there is no role hierarchy, and how to change a user's role.

Organization Setup

Creating an organization with the five-step wizard, then where departments, sections, budget codes, locations and user types are configured.

Previous

Company Settings

Next

Consultant Permissions

TravelFlow records significant actions to an audit log so you can see who did what, when, and in which module. The log supports dispute resolution, internal governance, and answering “who changed this?” after the fact. Every entry is written by TravelFlow's server when the action happens, naming the person who was signed in; nobody can add, change or delete an entry from their browser.

Who Can View the Audit Log

The audit screen is open to Super Admins, Organization Admins, Consultant Admins and Accountants. Non-super-admins see only their own organization’s entries; a Super Admin sees every organization.

Where to Find It

Click Audit in the admin navigation bar. The page is titled Audit Logs with the subtitle “System Activity Monitor”.

What Gets Logged

  • Creates — new records such as bookings, booking requests, invoices, quotations, journal entries, users and organizations. A booking request is recorded in the log of the organisation it was raised for.
  • Updates — edits to existing records, including the changed fields.
  • Deletes — removal or voiding of records.
  • Logins — authentication events, including a sign-in lockout after repeated failed attempts. Failed attempts are reported by the browser, unverified, so one entry is written when a lockout starts rather than one per attempt. A sign-in completed with two-step verification says which second factor was used, and adding or removing a second factor is recorded too.

Filtering the Log

Five controls sit above the table:

  1. Search logs — a free-text box. It filters the entries already loaded on the page, matching against user name, action, module, entity type, entity name and details. It is not a server-side search, so it only looks inside the batch currently displayed.
  2. Action — All Actions, Login, Created, Updated, Deleted, or Failed. Note that Failed filters on a failure status rather than on an action type.
  3. Module — restricts to one area of the system.
  4. Status — All Status, Success, Warning, or Failure.
  5. Date range — Today, This Week, This Month, or All Time.
Tip: There is no “user” dropdown. To trace one person’s activity, narrow the date range first, then type their name into the search box.

Exporting

Export Logs in the page header downloads the entries matching your current filters. A name or detail that starts like a spreadsheet formula (with =, +, - or @) is written with a leading apostrophe, so the spreadsheet shows it as text and never runs it.

Retention and Deletion

Audit entries are not permanently immutable. A Super Admin can purge old entries from Settings > General Settings using Purge Old Logs, which deletes everything older than the saved audit-log retention period. That deletion cannot be undone, and the purge itself is recorded in the log: who ran it, how many entries went and the cut-off date.

Sign-in and sign-out entries are also deleted automatically one year after they were made, by the daily clean-up; a failed sign-in entry holds the IP address and the e-mail address typed. Every other entry stays until it is purged.

Important: If your organization has a regulatory retention obligation, export the log on a schedule and keep the export outside TravelFlow. Do not treat the in-app audit log as tamper-proof evidence — a Super Admin can both purge it and, at the database level, alter entries.