Review User Actions, Employee Actions, Attendance and Schedule Logs

1. User Actions

User Actions records manager-app activity such as administrative changes, schedule decisions and workspace operations. Use it when you need to understand who changed manager-side data.

2. Employee Actions

Employee Actions records employee-originated Employee Hub activity for the exact active workspace. Keeping it separate from User Actions prevents manager/admin work and employee self-service activity from being mixed into one stream.

3. Attendance

Attendance shows Employee Hub clock activity for the exact active workspace, including clock-in, clock-out and break records where attendance data exists. The admin view refreshes so completed sessions can surface without managers relying on stale rows.

Attendance is not the same as timesheet correction. Editing payroll hours should not rewrite the underlying attendance history.

4. Schedule Logs

Schedule Logs remain the place to inspect Auto-Assign runs, diagnostics, saved assignment snapshots and schedule restore history. Use Schedule Logs for scheduling-engine traceability, not for employee clock records.

5. Where employee requests and manager decisions appear

Manager approvals and rejections for employee schedule requests and swaps appear in User Actions with the employee and date where available.

Employee-originated activity remains separate from manager actions. Schedule Logs continue to hold Auto-Assign run history and restore points.

6. Review saved Auto-Assign blocker evidence

Saved Auto-Assign logs keep the coverage evidence produced by the run. Use the recorded blockers and shortage context when investigating why a shift remained uncovered instead of reconstructing the reason from the current employee list alone.