The audit trail and what it captures
MobilityManager keeps an audit trail of changes to your tenant data so you can see who changed what and when. Entries are written automatically and cannot be altered afterward. This article explains what the audit trail captures and how it is recorded.
Required permission
Reading the audit trail requires the settings:view permission. The trail is read-only; it cannot be edited or deleted through the platform.
How entries are captured
The audit trail is populated automatically whenever tenant data is saved. Every insert, update, and delete on an audited entity produces an audit entry — you do not have to enable logging per record. Each entry records the acting user's email and ID along with the change details, and entries are stored in the tenant's own database, so they are scoped to that tenant.
What each entry contains
| Field | Description |
|---|---|
| AuditId | A unique identifier that groups related changes saved together in one operation. |
| EntityType | The kind of record that changed, for example Vehicle, Booking, or Driver. |
| EntityId | The primary key of the changed record. |
| Action | One of Insert, Update, or Delete. |
| Timestamp | When the change occurred, in UTC. |
| UserEmail / UserId | The email and ID of the user who made the change. |
| OldValues | The values before the change. Empty for inserts. |
| NewValues | The values after the change. Empty for deletes. |
| ChangedColumns | For updates, the specific columns that changed, each with its original and new value. |
| TableName | The database table the record belongs to. |
| AdditionalInfo | Optional extra context such as a correlation identifier. |
Note: For an update, only the columns that actually changed appear in
ChangedColumns, so you can see the precise before-and-after of each modified field.
What is not audited
A few record types are excluded to avoid noise and loops, because they are themselves a form of history:
- Audit entries (the trail does not audit itself).
- Belege (receipts) workflow events.
- Retention execution logs.
- Vehicle history entries (Fahrzeugakte history).
Records that were loaded but not changed are also skipped — only real inserts, updates, and deletes are recorded.
Tip: Use the
AuditIdto reconstruct a single business action that touched several records at once — all of its audit entries share the same identifier.
Related
- View and filter audit entries
- View the audit history of an entity
- Why audit entries cannot be edited or deleted
- Retention and compliance reporting
