Platform Dashboard
The enterprise master dashboard for queried customers, HRS distribution, billing usage, webhook health, exports, and customer-level drill-downs.
The dashboard keeps the customer portfolio, alerts, and consent-backed trend review in one operating surface.
Finance and compliance can pick up pending export jobs without leaving the workspace dashboard.
Employee access requests remain visible beside usage, billing, and key health.
It is designed as a real working dashboard, not a marketing summary, so teams can monitor trust workflows, manage projects, and investigate customer-level history quickly.
Drill-down surfaces support date filters, export actions, and audit-friendly timeline review while respecting the subject's active consent scope.
That is why the platform host opens here by default: the dashboard is where organizations understand what is healthy, what is drifting, and what needs action next.
{
"organization_id": "org_northstar_logistics",
"workspace_health": {
"projects": 3,
"healthy_keys": 4,
"pending_exports": 2,
"employee_approvals_waiting": 18
},
"portfolio": {
"queried_customers": 142,
"recoveries_flagged": 4,
"consent_expiring_soon": 3
}
}The platform dashboard should summarize the operational state first, then route the operator into the exact lane that needs attention.
The dashboard should show how many protected workloads are running before the operator drills into one.
Exports and scheduled packages should stay visible from the same control surface as customer and billing pressure.
The most immediate launch blocker should remain visible without opening a second review lane.
Technical and finance owners should see live spend without leaving the workspace.
Expiring visibility belongs beside project and customer pressure because it changes what the workspace can actually see.
Employee approval pressure should stay in the same operating picture as API and report health.
The master dashboard shows organizations, projects, current keys, total queried customers, recent HRS distribution, recent API usage, consent-state summaries, webhook health, and export/report shortcuts.
It is designed as a real working dashboard, not a marketing summary, so teams can monitor trust workflows, manage projects, and investigate customer-level history quickly.
Customer detail pages expose the permitted HRS trend graph, recoveries, declines, plateaus, consent timestamp, and relevant reliability events for that subject.
Drill-down surfaces support date filters, export actions, and audit-friendly timeline review while respecting the subject's active consent scope.
The dashboard is also the control surface for project health, export backlog, billing drift, approval queues, and webhook delivery. Operators should be able to move from one alert into the exact lane that can resolve it.
That is why the platform host opens here by default: the dashboard is where organizations understand what is healthy, what is drifting, and what needs action next.