The job of this console
Pick the grain you need, open that pack, drill to the source. Do not hunt for a number to edit on the hub.
Analytics · Hub
Analytics Hub
Launch pad onto domain analytics — workforce, delivery, finance, payroll — still composed from canonical registers.
Scroll to Flowcharts. Scenario: Pick a domain from the analytics hub.
Pack directory
A map of analytics, not a metric store
Analytics hub lists domain packs you are allowed to open. Numbers still live on employees, projects, contracts, and time — not on this directory.
Analytics → Analytics hub
Route
/analytics/hub
Org flag analyticsPlatformEnabled
Executive · Finance · HR Admin · Admin
Seat at the table
Executives, finance, HR admins, and admins with analyticsPlatformEnabled. Packs you cannot open stay hidden.
The working rhythm
Land, choose a pack, leave the hub, work the domain page.
Moments that bring you here
First visit to Analytics. After a flag is turned on. When you cannot remember whether payroll analytics is under Payroll or Analytics.
ⓘ
Directory only
Control tower is steering. Report builder is ad-hoc. This page only routes.
Flowcharts
1 — Choose a pack
Land on the hub, open one domain, leave the hub behind.
flowchart TD
A[Open Analytics hub] --> B[See enabled packs]
B --> C[Open a domain]
C --> D[Read that grain]
D --> E[Drill to source]
- 1OpenAnalytics → Analytics hub.
- 2ChooseWorkforce, delivery, finance, payroll, risk.
- 3ReadThat pack’s KPIs.
- 4DrillEmployee, Project, PO, Task.
Overview
The hub is a directory of analytics packs. It does not store metrics. Each pack still reads Employee, Project, PurchaseOrder, Task, TaskActivity, or payroll/finance registers.
How to use
1. Hidden packs are flags
Do not assume a missing tile means no data.
2. Not the report builder
Saved ad-hoc reports live on Report builder.
3. Masking follows persona
HR packs still hide pay you cannot see.