Audit log
Overview
The audit log records every writing action in the system — completely, not by sampling. Creating, changing, deleting and restoring are all captured, each with the state before and after.
The property that matters most day to day is the distinction of the actor: an entry states whether a human, the AI or an automation acted. That makes the question "who changed this?" answerable even when nobody was sitting at a screen — and those are exactly the cases that otherwise stay unexplained.
Core tasks
Find a change. The search field covers entity, action and actor. Filters for action, entity class, actor identifier and period are available as well; the period is set as a from–to date in YYYY-MM-DD form.
Read the before-and-after. Opening an entry shows the detail with Before, After and a list of the changed fields — you do not have to lay two states side by side, the comparison is already made.
Scan the list. Columns show timestamp, action, entity, object ID and actor.
Trace an action. Every entry carries a request identifier. Through it, all changes belonging to a single operation can be brought together — useful when one click touched several records behind the scenes.
Fields in detail
The log has no input mask — it is read, not written. Entries can neither be changed nor deleted; that is the point of a log.
| Element | From | What it means |
|---|---|---|
| Time | the booking | When it happened. |
| Actor | signed-in identity | Who did it. |
| Actor type | human, AI or automation | What acted. Precisely this distinction answers "surely that was none of us?" — an AI or an automation acts under the identity it runs on behalf of, but visibly as such. |
| Object | kind and identifier of the record | What was acted on, as a jump there. |
| Action | created, changed, deleted | What happened. |
| Before / after | value comparison | What changed, field by field. The actual content of the log. |
| Request id | the request | The bracket over everything that arose from one action. It lets a chain of consequences be traced instead of guessing at single rows. |
Filtering is by period, actor, object kind and action.
Settings & permissions
- Permission
platform.audit.read. Without it the page returns no entries. - Read-only. The log cannot be edited and cannot be deleted. That is the point: a log that could
be altered would not be one.
- Four actions. Created, Updated, Deleted, Restored.
- Four actors. Human, AI, Automation and — where no attribution was possible — Unknown.
FAQ & troubleshooting
I see no entries. Either you lack the platform.audit.read permission, or the filters cut too narrowly. Reset the period first.
A change is missing from the log. What is logged are writing actions. Pure reading, searching and exporting produce no entry.
**The actor is Unknown.** Then the action could not be attributed to an account — typical for operations from system start-up or from the setup process.
I want to restore an earlier state. The log shows the earlier state but does not restore it. For deleted records, the recycle bin is the route.