Employee Activity log
The Activity log helps you understand what happened to employee records and related workflows. Use it to identify the action, when it occurred, who performed it, and which changes were recorded.
Access needed
Access depends on your assigned permissions and workflow scope.
- Read one employee’s Activity log tab
employees.audit.readEntering through an employee profile separately needs employees.read.
Role and permission labels
Typical responsibility: Authorized employee-history reader. Role names alone do not grant access.
- Read employee history
- Read, filter, inspect and export this Activity log
audit.readReading the related business record does not automatically grant Activity log access. CSV export covers the loaded page.
Role and permission labels
Typical responsibility: Authorized investigator. Role names alone do not grant access.
- Read the service Activity log
Demo screenshots may show broader access than your account.
Choose the right view
| View | Use it when |
|---|---|
| An employee's Activity log tab | You are investigating one person's employee record and related contacts, dependents, compensation, requests, letters, job changes, or journeys. |
| Employees → Activity log | You need to search across employee-service activity, including records outside a single employee's profile. |
These views have separate access requirements. Being able to read an employee record does not automatically grant access to its activity history or the broader log. Ask your administrator if the view you need is unavailable.
Inspect one employee's history
- Open the correct employee
Find the employee, check their employee number, and open the full record.
- Select Activity log
Use the tab-strip arrows if the tab is off-screen. The employee history table shows Action, Record type, Changed by, Occurred, and the Changes count.
- Open the relevant event
Select its action or row. Check the event details, then inspect recorded changes where available. Use the page controls to reach other history entries.
Read event details
The details panel identifies the action, actor, record type, record reference, and occurrence time. A subject identifies the employee or related subject when supplied; some events do not provide it. Keep the event reference and time when asking an administrator to investigate a specific event.
A name can be shown when your account can resolve the user information. Otherwise an identifier may appear. Missing or unavailable names do not prove that the event failed. System-generated actions may be attributed to the system rather than an individual.
Compare recorded changes
Open Changes when available. Expand a field's Compare entry to inspect the previous and new values. Check the field name, action, and record type together: a created journey task, for example, is different from a change to the employee's own job details.
Personal information is deliberately redacted when activity is recorded. This can include personal contact details, birth dates, identifiers, addresses, photos, payment details, family records, compensation values and reasons, request snapshots, letter recipients and purposes, and journey-task notes.
Redacted values cannot be revealed by granting more access to the historical event. If you need to verify current information, open its authorized record separately. Do not interpret redaction as an empty value or try to replace it.
Search the broader Activity log
Open Employees → Activity log. Events are listed newest first. Use Filter to narrow the result rather than scanning every page.
| Filter | How it helps |
|---|---|
| Action | Find a particular kind of activity, such as creation or a workflow event. |
| Entity type | Focus on employee records, requests, letters, journeys, or other recorded types. |
| Actor | Find activity attributed to a specific user or actor reference. |
| Entity | Focus on a particular record reference. |
| Subject | Focus on the employee or subject associated with events. |
| From date and To date | Narrow the time period being investigated. |
Use the field values or references you know; do not assume an employee number and an internal record reference are interchangeable. Remove individual filter chips or use Reset to broaden the results again. Check pagination and Rows per page when more records match than are visible.
Export the current page
Export page CSV exports the currently loaded page of results, not the entire matching history. Set the intended filters and check the current page before exporting. Treat the file as internal activity information and follow your organization's handling rules.
What the log does not do
The Activity log is a record of actions, not an undo screen. Reading an event does not approve a request, complete a journey task, restore a record, or reverse an employment change. Use the appropriate workflow for any correction.
Not every process is represented in this log. Bulk-import jobs and their row results have their own import results rather than employee Activity log entries. For investigation, compare the relevant workflow's current state with the events you can access.
Troubleshooting
| Problem | What to check |
|---|---|
| Activity log is unavailable | Ask your administrator to review access for the specific employee history or broader log. |
| No events match | Remove filters, widen the date range, and check the employee or record reference. Distinguish an empty result from a loading error. |
| The actor is an identifier | User-name lookup may be unavailable or restricted; the event can still be valid. |
| Changes is zero or comparisons are absent | The event may not include field-level detail. Review its action, type, and time. |
| A value is redacted | This is intentional historical masking. Check the current authorized record if needed. |
| Export contains fewer rows than expected | Export page CSV includes only the loaded page. |
When requesting help, share the action, time, and event reference where appropriate. Keep private employee values and unrelated activity out of screenshots or support messages.