Skip to content

Logs & Audit Trail

Prove who changed master data, inspect field-level diffs, export evidence for auditors, and stream changes to external systems. Global audit query is Enterprise; version history is Professional+.

Audit log

The audit log is the authoritative record of MDM operations. Entries are stored in the configuration schema and include:

  • Who performed the action
  • Which entity was affected
  • Which record was affected
  • What action occurred
  • When it happened in UTC

Audit API

Requires Global Admin.

GET /api/v1/audit?entityName=Customer&user=jdoe@contoso.com&action=data_updated&fromUtc=2025-01-01T00:00:00Z&toUtc=2025-03-24T23:59:59Z&skip=0&take=50

Common filters:

  • entityName
  • user
  • action
  • recordId
  • fromUtc / toUtc
  • skip
  • take

Viewing the audit log

  • Filter by entity, user, date range, and action type.
  • Use pagination for large histories.
  • Sort by time to reconstruct incident timelines.

Export

CSV export produces a portable file for auditors, GRC tools, or spreadsheet analysis.

CLI usage

entihub audit --entity Customer --user jdoe@contoso.com --action data_updated --from-utc 2025-01-01 --to-utc 2025-03-24 --skip 0 --take 50
entihub changes --entity Customer --after-id 12345 --take 100

Change log API

GET /api/v1/changes?entity=Customer&afterId=12345&fromUtc=2025-01-01T00:00:00Z&toUtc=2025-03-24T23:59:59Z&take=100

Response entries use webhook-aligned action names such as data_created, data_updated, data_soft_deleted, data_deleted, data_restored, data_edited, and data_rejected.

Version history

For entities with historyEnabled, EntiHub keeps versioned rows with temporal tracking.

GET  /api/v1/entities/{name}/versions/{id}
POST /api/v1/entities/{name}/versions/{id}/restore

Retention

Configure audit retention with Mdm__AuditRetentionDays.

  • Default is 365 days.
  • Set to 0 or leave empty to disable automatic cleanup.