Dashboard
What this achieves
Section titled “What this achieves”The dashboard is the first screen you see after signing in, and it summarises the work waiting for you alongside the state of the people you are responsible for. What appears on it changes with your role, because Humavera never shows anyone figures they are not entitled to see.
One screen, assembled per viewer
Section titled “One screen, assembled per viewer”The dashboard is not a fixed report that everyone shares. Humavera builds it from the data your role can reach, so the same screen answers a different question depending on who opened it.
This is not a display preference. Access is default-deny: anything touching employee data must declare whose data it is asking for, and a manager is limited to their own reports. The dashboard inherits that rule rather than working around it.
Example: Priya Raman is an admin at HC Corp, so her dashboard counts across the whole company. Olivia Bennett, Head of Engineering, opens the same screen and sees her own engineers only — not Finance, not Sales, and not her peers’ teams.
| Option | Description |
|---|---|
| Admin | Company-wide counters across every department and legal entity. |
| Manager | A scoped view of their own direct reports, and the decisions waiting on them. |
| Employee | Their own records and their own outstanding requests. |
| Instructor | The learning they deliver, rather than company HR data. |
Why two people quote different numbers
Section titled “Why two people quote different numbers”A common support question is why two colleagues report different headcounts from “the dashboard”. Both are usually right. Each figure is bounded by what that person may see, so a manager’s total counts their reports while an admin’s counts the company.
Example: if Olivia Bennett quotes the size of her engineering team and Priya Raman quotes the company total, neither number is wrong. They are answers to different questions.
What the dashboard is not
Section titled “What the dashboard is not”The dashboard is a summary and a starting point. It is not the reporting system, and it is not the audit trail.
| Option | Description |
|---|---|
| Dashboard | A live summary of the current state, scoped to you, meant for a glance at sign-in. |
| Insights and analytics | Deeper analysis, saved and scheduled reports, and the executive view aggregating flight risk, workforce, capability, and org goals. |
| Activity | The running record of what changed, who changed it, and when. |
What happens next
Section titled “What happens next”Use the dashboard to find the thing that needs you, then move into the section that owns it. Managers usually continue to their team cockpit to act on what surfaced; admins usually open the module a counter refers to. When you want analysis rather than a status glance — trends, comparisons, or a report you can schedule and share — that work belongs in insights and analytics.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved