The job of this console
See where the org moved, open the person or case, change the source, let the pack refresh.
Analytics · People
Workforce Analytics
Headcount, joiners, attrition, and attendance themes on Employee — charts, not the employee file and not payroll.
Scroll to Flowcharts. Scenario: Read workforce analytics then open an employee.
People grain
Headcount stories on the employee file
Workforce analytics rolls up Employee movement, attendance themes, and lifecycle. It does not replace the directory, ATS, or payroll.
Analytics → Workforce analytics
Route
/analytics/workforce
Org flag workforceEnabled
HR Admin · Executive · Admin
Seat at the table
HR admins, executives, admins with workforceEnabled. Managers see only scoped teams.
The working rhythm
Period filter, read movement, drill a cluster, act on Employees or cases.
Moments that bring you here
Monthly HR pack. A spike in leavers. Headcount vs plan. After a hiring freeze question.
ⓘ
Employee is the person
Candidates stay in recruiting. Pay stays in payroll. Ratings stay in reviews. Mask what this pack must not show.
Flowcharts
1 — Movement then the person
Read workforce KPIs, open the Employee or case.
flowchart TD
A[Open Workforce analytics] --> B[Read headcount]
B --> C[Joiners / leavers]
C --> D[Employees / cases]
D --> E[Act on Employee]
- 1OpenAnalytics → Workforce analytics.
- 2ScanHeadcount and movement.
- 3DrillTeam or case cluster.
- 4ActEmployees, onboarding, offboarding.
Overview
Workforce analytics composes Employee, attendance, and lifecycle cases. It is not recruiting ATS and not payroll. Performance ratings do not belong unmasked here.
How to use
1. Recruiting is upstream
Candidates are not Employees until hired.
2. Attendance grain
Matrix still owns marks.
3. Mask
No salary series unless the persona grant allows payroll analytics instead.