MaintIQ / Help Center

Exporting audit logs from MaintIQ

Updated May 18, 2026

Auditors, insurers, and your own analytics stack will eventually ask for a copy of your activity log. MaintIQ exports History in formats they can ingest.

CSV export

  1. Open History.
  2. Apply the filters you want (date range, type, user).
  3. Click Export → CSV.

The download includes one row per event with columns:

  • event_id
  • timestamp_utc
  • actor_id
  • actor_email
  • action
  • object_type
  • object_id
  • facility_id
  • old_value (JSON)
  • new_value (JSON)
  • ip_address

CSVs are capped at 50,000 rows per file. If your filter returns more, MaintIQ splits the export into multiple files.

JSON export

For programmatic ingestion, pick Export → JSON. The structure mirrors the CSV columns with old_value and new_value as native JSON objects rather than strings.

Scheduled exports

On Growth and Scale plans, admins can configure scheduled exports in Admin → Integrations → Audit export:

  • Frequency: daily, weekly, monthly.
  • Destination: email, S3-compatible bucket, or HTTPS webhook.
  • Format: CSV or JSON.
  • Filter: a saved History view.

What to keep for SOC 2 / ISO 27001

If you are building toward certification, the standard ask is:

  • All access events (logins, role changes) for 1 year.
  • All change events on production data for 7 years.
  • A documented retention policy stored alongside the logs.

MaintIQ's retention defaults exceed the SOC 2 minimum. Your auditor will usually accept the scheduled monthly export landing in your own bucket as evidence.

Verifying integrity

Each export includes a SHA-256 checksum in the filename and in the download dialog. Store the checksum alongside the file — it lets you prove the log has not been tampered with after delivery.

Permissions

Only Admin and Auditor roles can export. Exports are themselves logged in History (so you can see who pulled what, when).