Audit Trail report
Use the Audit Trail to find out who changed an employee's record, what they changed and when, such as who changed this salary or edited a bank account. It shows the old and new values, whether it was a person, a bulk import or the system, and flags changes that look suspicious. It answers "this was different last week, who changed it?"
Where: My Team › Tools & Reports, under Reports, select Audit Trail. The page itself is headed Profile Data Audit.
You need:
- The My Team Reports right to open it
- The Anomaly Review right for the Anomaly review view
- The Audit Sensitive Fields right to choose which fields count as sensitive
⚠️ The trail keeps 6 months. Older changes are deleted automatically, so the longest preset is Last 6 months and a custom range cannot start earlier. Export anything you need to keep.
How to find out who changed something
- Select the period. The page opens on Last 30 days. Choose Last 24 hours, Last 7 days, Last 30 days, Last 90 days or Last 6 months, or enter a Custom range with From and To, then select Apply.
- Choose Employee to pick whose record it is. Choose Changed by to pick who made the change. You can also type either name into the search box.
- To narrow further, select More, then Record type, Category or How.
- Read the rows: When, Employee, Field, Change (old to new value), Changed by and How.
- Select Detail on a row for the full record, including who approved it and any request reference. From there, All changes by this person lists everything that person changed.

The chips narrow it in one click: Sensitive fields only, Changed by someone else and bulk import or API.
How to see changes to company settings
- In the view switcher, select Settings. It sits next to Changes and Grouped by save.
- Read the list. It covers company settings and configuration, meaning everything that is not an employee record.
How to see everything saved at once
Select Grouped by save. Fields changed in the same save appear together, which makes one edit of ten fields read as one event. Select Changes to go back to one row per field.
How to ask in plain words
If your company has KAMI AI and you hold the My Team AI tasks right, a KAMI AI box sits above the controls.
- Type a question, such as "What changed in payroll settings this month?"
- Select Ask. Kita picks the filters and answers from the trail, and the matching rows show below so you can check the answer.
Hide KAMI AI folds the box away, and Ask KAMI AI in the controls brings it back.
How to choose which fields are sensitive
- Select the shield button next to Export.
- In Configure sensitive fields, tick or untick fields in each category. The count at the top shows how many are marked.
- Select Save.
Without the Audit Sensitive Fields right you can see the list but not change it. The setting drives the Sensitive fields figure, the Sensitive fields only chip and the anomaly review.
How to check for suspicious changes
- Set the period, then select Anomaly review.
- Select Run review.
- Open a finding to see the exact changes behind it.
- Select Confirm or Dismiss. Decisions are kept in the Audit log.
- To keep the findings, select Export under the list. It downloads them as a CSV file.
If the data has changed since the last run, the page says Data may be stale — re-run the scan.
| The review looks for | Means |
|---|---|
| Self-edits | Someone changing their own sensitive details, unless it came through an approval |
| Role and scope | A sensitive field changed by a role that would not normally change it |
| Bursts | One person changing 6 or more employees within 24 hours |
| Bulk sensitive changes | Sensitive fields rewritten by import or API in batches of 3 or more, with no approval |
| Support access | Sensitive changes made by a support login |
| Off-hours | Sensitive changes outside 7am to 8pm, or on the person's rest day |
Detection follows fixed rules, so a finding is a prompt to check and not a verdict.
How to export it
Select Export in the controls. A CSV file of what the current filters show downloads straight away.
What it records
- Every route: a profile edit, a Profile Manager edit, a bulk import, the API, and KAMI itself, such as automatic deactivation on a last day. Tags show System, API and support changes.
- Changes only: it does not record who viewed a record.
- The figures at the top: the number of changes, how many touched Sensitive fields (pay, banking, statutory IDs), Employees affected, Who made them with the self-service share, and how many were Not via the app.
System field changes are hidden by default. Select Show system fields to see them. Row density at the bottom switches between Comfortable and Compact.
What you can see depends on your rights. Sections you have no right to are left out. Sensitive values show as dots if you lack the right for that category. You only see changes to your own profile with the My Profile Audit right.
What Happens Next
The trail is read-only. Nothing here changes a record, though confirming or dismissing a finding is itself recorded.
- An unexpected change: talk to whoever made it. It is usually a misunderstanding.
- Corrections to the same field again and again: the process is wrong, not the people.
Tips
- Check it before assuming a bug. "The system changed it" usually turns out to be a person, and the trail settles that quickly.
- Investigate a wrong payslip here. The date of the change tells you whether one period was affected or several.
- Export when a dispute starts, before the changes age out at 6 months.
- Do not use it to watch individuals routinely. It is an investigation tool.
Troubleshooting / FAQ
Q: Who changed this employee's salary? Choose them under Employee, then select Sensitive fields only and look for the wage field.
Q: A change I know happened is not showing. Check the period. Then check it is under 6 months old, that Show system fields is on if KAMI made it, and that you have rights to that section.
Q: Can I see changes from last year? No. History is kept for 6 months, then deleted automatically.
Q: Hundreds of entries appeared at once from one person. A bulk edit or import. Each change has its own row, all under the person who ran it. Select bulk import or API or Grouped by save.
Q: Why are some values dots? You lack the right to that category, such as banking or payroll.