Attendance Activity log
Use the Activity log to investigate what happened to an attendance record or timesheet: the action, who performed it, when it occurred, and the recorded changes. Reading history does not change attendance or decide a timesheet.
Access needed
Access depends on your assigned permissions and workflow scope.
- 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.
Open the right log
Open Attendance → Activity log. This is the attendance history, separate from the Employee Activity log. Access to daily attendance or your own timesheet does not automatically grant access to this log. Ask your administrator if it is unavailable.
The columns show Action, Entity type, Occurred, Actor, Entity, Subject, and Changes. Entity identifies the record involved; Subject identifies the employee when supplied. A record reference is different from an employee number.
Our screenshots show actual events from fictional demo attendance: record creation, a clock-out update, and a submitted timesheet. Names and dates illustrate the workflow; use your own workspace's records when investigating.
Find an event
- Choose the question you are investigating
Start with the employee, record, action, or approximate time you know. For a weekly submission, distinguish the timesheet from the individual daily attendance records.
- Narrow the list
Open Filter. Use Action for a specific event, Entity type for the kind of record, and From date and To date to narrow the period. Actor, Entity, and Subject filters help when you know the relevant person or reference.
- Check the applied filters
Read the filter chips and matching rows. Remove an individual chip or use Reset to widen the search. Check the page controls when more results match than fit on one page.
- Open the action
Select the action button in the relevant row. Check the employee, record reference, and occurrence time before interpreting the event.
For example, TimesheetSubmitted finds submission activity. It does not mean the week was approved. Several events can refer to the same record: a creation event and a workflow event are not necessarily duplicate attendance entries.
Read Details
Select Details in the event panel. Review the occurrence time, action, actor, entity type, entity reference, subject, and event reference. Keep the event reference and time when requesting help with a particular event.
The list may show a relative time such as “an hour ago”; inspect the timestamp for the exact occurrence. Actor names can fall back to identifiers when name lookup is unavailable or restricted. System-generated events may identify a service instead of a person. A missing name is not evidence that the action failed.
Compare recorded changes
Select Changes, then expand a field's Compare entry. Before and After show the values recorded for that event. Use Search changed fields and values to find a field in a longer comparison.
In the example, Approval Step changes from Not set to Hr when the week is submitted for HR review. That is historical evidence of submission, not evidence of a later approval. Check the timesheet for its current state.
The Changes count reflects supplied field-level detail. Zero changes does not mean nothing happened. Sensitive values can be hidden intentionally; a hidden value is not an empty value, and historical masking cannot be undone by opening the event with more access.
Investigate leave and attendance conflicts
An event named LeaveOverlapsAttendance means approved leave encountered an attendance record already present on the date. Review its recorded details, then inspect the authorized leave request and attendance record before arranging a correction. Do not add another attendance record to make the event disappear.
When Open attendance record is offered for a conflict, it opens the related record under your existing attendance access. The shortcut is not a correction or an approval. If it is unavailable, use the relevant authorized record view or ask HR to investigate.
Export a page
Set the intended filters and page, then select Export page CSV. This exports the currently loaded page, not every matching event. Handle the file as internal activity information and follow your organization's sharing rules.
Keep history separate from corrections
Use Daily attendance records for permitted corrections and Review employee timesheets for review decisions or reopening. The Activity log is not an undo screen. Do not infer current record status from an older event alone.
Holiday settings have a separate organization workflow. Do not expect an Attendance Activity log entry merely because a holiday was added or renamed.
Troubleshooting
| Problem | What to check |
|---|---|
| Activity log is unavailable | Ask your administrator to check access to attendance history. |
| No matching events | Widen the date range, clear filters, and verify the subject or record reference. |
| An actor appears as an identifier | Name lookup may be unavailable; retain the recorded identifier for investigation. |
| Changes are absent or hidden | Check the action and details; field comparisons may be absent or intentionally masked. |
| A submission event exists but the week looks different now | Review later events and open the current timesheet. |
| CSV contains fewer events than expected | Export page CSV includes only the loaded page. |
Share only the event information needed for an investigation. Keep unrelated employee information out of screenshots and support messages.