HR
How do we design manager-safe analytics queries?
Keep workforce questions scoped, aggregated, and aligned with what managers are allowed to know about their teams.
- analytics
- managers
- hr
If managers may use employee analytics, each question should respect people data norms and your internal access rules.
Prefer aggregates over lists
- Ask for counts and breakdowns (“how many in my team are in {location}”) rather than unnecessary rosters unless policy allows.
- Avoid combining attributes that could re-identify someone in a small team.
Anchor on official org data
- Phrase filters using HRIS fields your company trusts: department, location, tenure bands—not informal chat labels.
Example
A line manager asks: “Headcount in my team by country.” The answer returns numbers only if their permissions include those employees. They do not see salary or performance ratings through the same path.
Guardrails
- If your organization limits managers to direct reports only, verify that limitation in Harriet matches your HR policy—IT and HR should align on configuration.
- Never paste analytics results into public Slack channels.
Use Harriet in your organisation for searchable help, AI assistance, and your company knowledge base.
Log in to Harriet