Skip to content

Audit logs

Every important action in your FSM Navigator® account is recorded in the audit log. Use it to track who did what, when, and why — giving you full visibility into your team's activity and a reliable record for accountability.

Who can see this

Audit logs are included on every plan. Access is limited to the Owner and Administrator roles — Dispatchers and Technicians will not see this section.


Before you start

  • You are signed in as an Owner

Open the audit log

  1. Click Reports in the sidebar.
  2. Select Audit Logs.
  3. The log viewer opens with the most recent activity displayed first.

What gets logged

FSM Navigator automatically records actions across every area of the platform. You do not need to enable logging — it runs continuously in the background.

Category Example actions
Authentication Sign in, sign out, failed login attempts, password changes
Jobs Job created, status changed, technician assigned, job deleted
Customers Customer added, customer updated, location modified
Invoicing Invoice generated, invoice sent, payment recorded, refund processed, invoice voided
Team User invited, user deactivated, role changed
Settings Company information updated, notification preferences changed, MFA enabled
Inventory Stock transferred, part added, low-stock alert triggered
Assets Asset created, maintenance scheduled, status changed, asset transferred

Each log entry includes:

  • Date and time of the action
  • User who performed the action
  • Action type describing what happened
  • Details with additional context (e.g., which job was updated or what status it changed to)

Filter the audit log

Use the filter controls at the top of the log viewer to narrow down results.

Filter by date range

Select a start and end date to view activity from a specific period. This is useful for investigating incidents or reviewing activity during a particular week or month.

Filter by user

Choose a specific team member to see only their actions. Use this to review an individual's activity or verify that a particular change was made by the right person.

Filter by action type

Select one or more action categories to focus on a specific type of activity. For example, filter to Invoicing actions to see all invoice-related changes, or filter to Authentication to review sign-in activity.

Search within logs

Use the search box to find log entries containing specific text. Search by job title, customer name, user name, or any keyword that appears in the log details.


Read a log entry

Each row in the audit log shows:

Column Description
Timestamp When the action occurred, displayed in your company's timezone
User The team member who performed the action
Action A summary of what happened (e.g., "Job status changed")
Details Additional context such as old and new values, affected entity, or reason
Severity Indicates whether the action is informational, a warning, or critical

Click on any row to expand it and view the full details of the action, including before-and-after values for changes.


Export audit logs

To save audit log data for external analysis or compliance:

  1. Set your desired filters (date range, user, action type).
  2. Click the Export button.
  3. The filtered log data downloads for your records. Large exports show a running row count on the button while they are prepared, then download as a single CSV file (up to 100,000 rows per export — narrow the date range to capture everything in very large logs).

Every export is itself recorded in the audit log, with the number of rows it delivered. That applies to audit log and support access log exports, KPI report and time and attendance exports, and the inventory year-end tax report, as well as the customer, invoice, inventory and asset exports that were already recorded.

Regular exports

Export your audit logs monthly to maintain an external archive for compliance or auditing purposes.


Common use cases

Scenario How to investigate
"Who changed this job's status?" Filter by Jobs actions and search for the job title
"When did a user last sign in?" Filter by Authentication and select the user
"Who voided this invoice?" Filter by Invoicing and search for the invoice number
"What settings were changed this week?" Set the date range to the current week and filter by Settings
"Did anyone modify customer records?" Filter by Customers and review the entries

Frequently asked questions

How long are audit logs retained?

Audit logs are retained for a minimum of three (3) years. You can review activity going back to the day your account was created.

Can I delete audit log entries?

No. Audit logs are immutable — entries cannot be edited or deleted by anyone. This ensures a reliable, tamper-proof record of all activity.

What happens to a team member's name after I remove them?

New log entries record who acted by their account, not by their name, and the name is looked up each time you view the log. After you remove a team member, entries they made show Deleted user instead of their name. Entries recorded before October 26, 2026 may still contain the name as part of the original record. Those entries are kept unchanged as a security record, because the log cannot be edited. The same applies to the person an entry is about: when you delete, update or re-enable a team member, the entry records which account it was, and the name shown is looked up when you view the log. A removed team member shows as Deleted user. This also covers settings changes, estimate approvals and rejections, invoice line adjustments, authenticator resets and support sessions where our team signs in as one of your users: each entry records the account, never a stored name or email.

Can Dispatchers or Technicians view audit logs?

No. Only Owners can view audit logs. See Roles and permissions for details.

Are automated actions logged?

Yes. Actions triggered by the system — such as auto-assignment, recurring job creation, and SLA expiration — are recorded alongside manual user actions.

Do audit logs affect performance?

No. Logging runs in the background and does not impact the speed or responsiveness of the application.