Dashboard overview (home screen)

The operator landing page at /[lang]/dashboard/overview serves owners, admins, and coaches; members are routed to their member home.

Layout

The composition is:

1. Action Center — severity-ranked work from the 20-rule Insights catalog, with an explicit all-clear empty state. Owner/admin receive the full catalog; coaches receive seven operations/engagement rules.
2. Today / tasks working row — the whole org-local class day and the existing pending-task workflow. Schedule/coaching delivery modes determine whether the class panel applies; task permission determines the task panel.
3. Trends — member growth (analytics:view), revenue (analytics:view + paymentAnalytics:view + active payment provider), and leads (leads:manage). Inapplicable panels are omitted.
4. Coaching roster — for orgs with coaching programs, scoped to active coaching enrollments; due-today, seven-day completion, and needs-attention figures belong to its own header.

There is no Pulse strip or standalone KPI strip on Overview. The Reports KPI snapshot belongs only to the Reports workspace. Delivery modes come from active programs, not organization_type.

Populations, destinations and Reports

• Insight rows count each person once, carry sample actions, and use exact destinations.
• The Reports workspace and sidebar entry require analytics:view. They do not change Overview.
• Supported Tasks, Payments, and program-schedule URL hydration is unconditional.

Insight.drilldownHref is string | null. Null means an honest nonlinked row, with bounded member/session sample actions or an existing inline form queue where available—not an invented filter on a generic list.

Adjacent owning surfaces

Open cancellation requests/notices are retention cases, worked through cancellation_review tasks. The Members ending filter remains separate roster context. Members’ own ribbon shows total roster/commercial donut, trained this week, new this month, and churned this month, with imported and at-risk callouts; it has no Ending soon tile.

Docs

• Behavior — composition, flags, actionable routes, ownership.
• Code map — current panels, APIs, dictionaries, and routes.
• QA plan — role/mode/flag/navigation scenarios.
• Insights catalog — all 19 identifiers, exact ON/OFF counts, severities, and destinations.