Executive dashboard (/dashboard)
Purpose
The dashboard is the first Mission control landing for roles that manage lending and risk day-to-day. It summarizes volume, quality, and exceptions so leaders can ask better questions-not replace formal MIS.
What you typically see
- Date range control affecting all tiles in view-changing the range refetches summaries (you may see a short loading state).
- KPI sections aligned to your deployment: pipeline, approvals, risk flags, collections pressure, etc. (exact tiles vary by tenant configuration).
- Drill-down links (where implemented) that jump to filtered applications, approvals, or analytics lists.
What you should do
- Pick the date range that matches the committee question (last 30 days, month-to-date, quarter).
- Scan exceptions first (red / amber badges, “requires attention” rows).
- Drill only into areas you own-avoid exporting large extracts without data handling approval.
Trust and refresh
- Numbers are as of the last successful refresh; if something looks stale after a major operational event, use the page refresh control and wait for loading to finish.
- Keyboard shortcuts or a command palette may exist in your build-document them locally after QA confirms.
Who has access
Roles in DASHBOARD_PARENT_ROLES in constants.ts receive the clickable dashboard parent link; others may see group labels without the same parent navigation-your bank’s admin can confirm.