Skip to content
MaxTrax Help

Audit log & traceability

Traceability is a core quality-control concern, so MaxTrax keeps an accountable record of who did what and when. There are two complementary trails: an admin activity trail you view in the app, and a project activity audit-log report you obtain as a spreadsheet.

Before you start

Section titled “Before you start”
  • Viewing the admin activity trail needs a Corporate Administrator role or higher.
  • Requesting the project activity audit-log report needs write access to the project (a Weld Associate role or higher) — deliberately tighter than plain viewing.

The admin activity trail

Section titled “The admin activity trail”

The audit log screen in the admin area lists administrative actions, newest first, with these columns:

  • When — the time of the action, shown in your time zone.
  • Actor — who performed it.
  • Action — what they did.
  • Target — the user or record affected (or a dash when there isn’t one).
  • Outcome — success or denied. Denied attempts are recorded too, so a blocked action still leaves a trace.
  • Change — the resulting state of the affected record.

What it records

Section titled “What it records”

Administrative changes across the project, including: user invites and invite redemptions; locking and unlocking accounts; deactivating and reactivating accounts; role changes and project-scope (permission) changes; custom-field changes; global-settings and project-settings changes; branding changes; custom-report changes; personnel anonymization; and scheduled-report changes.

The project activity audit-log report

Section titled “The project activity audit-log report”

The audit-log report is a spreadsheet (.xlsx) of a single project’s activity trail — one row per recorded entry — with four columns:

  • Timestamp — when the action occurred, converted to your time zone.
  • Type — the friendly event type: a readable event name rather than an internal identifier, for example “Welder Assigned”. Acronyms are preserved, so you get “NDE Inspection Created” and “ISO Project Assigned”.
  • User — who performed the action (their display name, falling back to their user name).
  • Message — the readable message: a plain-language description of what happened, not a raw data dump. Sensitive values are left out, and an event type that has no curated description falls back to a safe field summary rather than exposing raw internal data.

Coverage

Section titled “Coverage”

The report is scoped to a single project and fail-closed to it. Its coverage includes deactivated projects — a deactivated project’s trail still prints, under that project’s name, so retiring a project never hides its history. Values are protected against spreadsheet formula injection, since the report is opened in a spreadsheet application.

How to obtain it

Section titled “How to obtain it”

The report is generated on the server and delivered as a secure download, the same way MaxTrax’s other server-side reports are — see Generate reports for how that flow works and the report catalog for what each report contains.

Section titled “Related”