Audit Trail
The Audit Trail records who changed what in employee data, and when - for example a corrected working time, a new bank account, or an updated tax ID. It lets you trace which change was made, at what time, and by whom.
Currently logged are time tracking (every change, including clock-in/clock-out, approving and reopening a month) and employee master data (create, update, terminate). The remaining HR areas are being added step by step; while an area shows no entries yet, that is not a filter at work.
| Employee | Field | Old Value | New Value | Timestamp |
|---|---|---|---|---|
| A. Beispiel | Weekly hours | 32 | 40 | 12 Aug 2026 09:14 |
| B. Muster | Department | Sales | Customer Success | 11 Aug 2026 16:02 |
/hr/auditWhat can I do here?
- See key numbers for the last 30 days at a glance (number of changes, most common area, most common action)
- Filter the log by area, action, and date range
- Open a single log entry and compare the old and new value in detail
Step by step
Find changes for a specific area
- Open Audit Trail.
- In the "All Areas" filter, pick the area you want, e.g. "absence" or "bank_info".
- Narrow further with the action and date range (from/to) filters if needed.
View a single change in detail
- Click the entry you want in the list.
- The side panel shows employee, area, action, the changed field, old and new value, who made the change, the timestamp, and — if recorded — the IP address.
Fields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Employee | The person whose data was changed | — |
| Area | Data area of the change | See the value list below |
| Action | Type of change | See the value list below |
| Field | The specific data field that was changed | Only populated for single-field changes |
| Old Value / New Value | Values before and after the change | Only populated together for "update" actions |
| Changed By | The person or system that made the change | — |
| Change Type | Whether the change was made by an admin, by the employee themselves, or automatically by the system | — |
| Timestamp | Date and time of the change | — |
| IP Address | IP address the change was made from | Only present when captured at the time the entry was written |
Values & statuses
Area
| Value | Meaning |
|---|---|
| employee | Employee master data |
| contract | Employment contract |
| absence | Time off |
| time_entry | Time-tracking entry |
| bank_info | Bank account |
| insurance | Insurance |
| tax_info | Tax data |
| emergency_contact | Emergency contact |
| id_document | Identity document |
| permit | Residence/work permit |
| qualification | Qualification |
| language | Language skill |
| report | Report |
Action
| Value | Meaning |
|---|---|
| create | A new record was created |
| update | An existing record was changed |
| delete | A record was deleted |
| approve | A request was approved |
| reject | A request was rejected |
Frequently asked questions
Can I edit or delete a log entry?
No. The audit trail is read-only — it exists purely to provide traceability and can't be changed from this page.
Why do some entries not show a "field"?
Not every action relates to a single field — for example, creating or deleting an entire record doesn't log an individual field.
How far back does the log go?
The stats at the top (changes, most common area, most common action) cover the last 30 days. The list itself can show older periods using the "from"/"to" filters.
Does every change in the system automatically create an entry?
Not everywhere yet. Time tracking and employee master data are logged in full; the remaining HR areas are being connected one after another. An empty area therefore does not mean nothing was changed there - it means logging has not reached it yet.