How do employee analytics permissions work?

Who can run workforce analytics in Harriet depends on roles, features, and any metadata scoping your admins configure.

Employee analytics lets authorized users ask structured questions about your workforce (counts, filters, breakdowns). Access is not automatically universal.

Typical controls

Plan and features: Analytics may require the appropriate capability on your Harriet subscription.
Roles: Only users with permission to use analytics (often HR admin or owner-style roles) should see or run it.
Metadata scoping: Some accounts limit which employees an admin can see based on org attributes (for example region or business unit). If configured, analytics results should respect that boundary.

What IT and HR should agree

Which roles may run workforce-wide reports versus scoped reports.
Whether managers get any analytics access or only HR.
How changes to HRIS reporting fields affect who appears in which scope.

Example

A country HR lead may be limited to employees in their country metadata, so their analytics questions never return headcount for other regions.

Guardrails

Treat analytics like any sensitive reporting tool: least privilege, audit who has access, and remove access when roles change.
If results look wrong, verify HRIS reporting metadata and mappings before assuming a Harriet bug.