| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Attendances (hr_attendance) • Discuss (mail) • Time Off (hr_holidays) • Calendar (calendar) |
| Community Apps Dependencies | Show |
| Lines of code | 7368 |
| Technical Name |
eh_hr_dashboard |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
EH HR Dashboard
Your HR command center, one click deep.
Why this module
EH HR Dashboard
Server-side aggregation
Instead of firing a separate count per tile from the browser, the board calls one backend method that aggregates every KPI in a single round trip. Today's attendance is one grouped read; the rest are guarded counts.
Counts you are allowed to see
Aggregation runs under the calling user's record rules, so each tile reflects only what that user may read. The numbers match the list the tile opens, with no separate permission model to keep in sync.
One missing module never breaks it
Tiles whose source model is not installed, or is unreadable, return a dash rather than throwing. The grouped attendance read falls back to per-status counts if the read signature differs, so the board stays up.
Day in the life
Open the board, act, drill in
An HR officer opens the HR Platform menu and lands on the dashboard. The Today group shows present, on leave, absent and anomaly counts for the day. Pending your action lists leave, overtime, loans and approval requests waiting on them. Workforce shows headcount, new hires this month and approved leaves this month. They click the leave-to-approve tile and the matching pre-filtered list opens directly, ready to action. Refresh re-runs the single aggregation call.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Overtime, loans and approval-request models are read defensively. If the module is not installed or the model is unreadable, _safe_count returns None and the tile renders a dash instead of breaking the whole board.
Counts are computed server-side under the calling user's record rules, so a user sees only the figures they are entitled to read, and the tile total agrees with the filtered list it opens.
Today's attendance is a single read_group by status. If the read_group signature or availability differs, the code falls back to a guarded count per status so the Today group still resolves.
If the whole aggregation call raises, the OWL board catches it and renders empty values rather than crashing the client action; headcount is the one count asserted to always return a real number.
A tile whose value is None or undefined is not marked clickable and openKpi returns early, so a dash tile cannot launch an empty or misleading list.
The dashboard menu is restricted to the HR officer group, so the command center is not exposed to every employee by default.
What is inside
Built to do the job, end to end.
- One aggregation model. A single AbstractModel, eh.hr.dashboard, exposes get_dashboard_data. It returns all 11 KPI keys the OWL board expects in one call. It owns no stored data and adds no tables.
- OWL client action and menu. A client action (tag eh_hr_dashboard.main) and a Dashboard menu under the HR Platform root, gated to the HR officer group. The component renders three groups of tiles from a single KPI descriptor list.
- Shared component kit. The board is built from the platform's shared OWL components, HrCard and HrStat, imported from eh_hr_core. It styles only its own grid and tiles; the look stays consistent with the rest of the suite.
- Eleven KPI tiles. Today (present, on leave, absent, anomalies), Pending your action (leave, overtime, loans, approval requests) and Workforce (headcount, new this month, leaves approved this month). Each tile knows the model and domain it both counts and opens.
- Click-through to native lists. Clicking a tile opens an act_window on the same model and domain it counted, in list then form view, in the current breadcrumb. The dashboard is a launch pad into standard Odoo lists, not a dead end.
Honest about the edges
What this does not do, so nothing surprises you.
- Read-only overview. The dashboard counts and links; it does not approve, edit or post anything. Actions happen in the lists it opens.
- It owns no business models. Every number comes from other platform modules, so a tile is only as populated as the module behind it.
- Three modules are hard dependencies (eh_hr_core, eh_hr_attendance_pro, eh_hr_leave_pro, plus hr). The overtime, loan and approval-request tiles depend on those optional modules being installed; absent, they show a dash.
- Counts refresh on load and on the Refresh button. There is no live push or auto-polling; the figures are point-in-time when the board is opened.
- No configuration screen. The KPI set and groupings are fixed in the component; tiles are not user-editable from the UI.
- Targets Odoo 17 Community. It is not an Enterprise dashboard widget and does not embed charts or spreadsheets.
odoo 17 hr dashboard, odoo human resources dashboard, hr kpi dashboard odoo, owl backend dashboard odoo 17, hr command center odoo, attendance overview odoo, leave to approve dashboard, pending approvals worklist odoo, headcount kpi odoo, odoo community hr overview, hr manager dashboard odoo, self hosted odoo hr dashboard
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Please log in to comment on this module