1In one sentence#
The Dashboard is LumosCRM's command centre — the authenticated landing page every user sees first, giving them a personalised greeting, the business's key numbers, what needs their attention right now, what's on today, and a live feed of recent activity — all scoped to what they're entitled to see.
It turns "log in and wonder what to do" into "log in and know exactly where to start."
2Who it's for#
Everyone who logs in. It adapts to the user's role and data scope, so a relationship manager sees their work and a leader sees the wider picture.
3The core idea: three bands of "what matters now"#
The dashboard organises everything into three groups that load progressively so the page is instant:
┌─────────────────────────────────────────────────────────┐
│ Good evening, Alex — Monday, 23 June 2026 [period][€] │
├─────────────────────────────────────────────────────────┤
│ STATS KPIs · revenue trend · receivables aging · │
│ requests by status │
├─────────────────────────────────────────────────────────┤
│ WORK action queue · open requests · today's schedule │
├─────────────────────────────────────────────────────────┤
│ FEED recent activity · upcoming reminders │
└─────────────────────────────────────────────────────────┘
A period and currency selector at the top reshape the figures, exactly like the Reports module — and the dashboard reuses the same visual building blocks for a consistent feel.
4What's on the dashboard#
Header#
A time-aware greeting (name + salutation + today's date), with period and currency selectors.
Stats band — the numbers#
- KPIs — the headline business metrics for the period.
- Revenue trend — income over time.
- Receivables aging — how much is outstanding and how overdue.
- Requests by status — the shape of the current service workload.
Work band — what needs doing#
- Action queue — the prioritised list of things needing attention (paginated).
- Open requests — live service requests.
- Schedule — what's coming up.
Feed band — what's happening#
- Recent activity — a live feed of changes across the CRM.
- Reminders — upcoming reminders.
Each band loads on demand (deferred), so the page appears immediately and fills in as data arrives.
5Capabilities at a glance#
| Capability | What it means |
|---|---|
| Personalised landing | A greeting and a view tailored to the logged-in user. |
| Period & currency controls | Reshape the figures to any window and currency. |
| Headline KPIs | The business's key numbers at a glance. |
| Revenue & receivables | Income trend and outstanding-money aging. |
| Workload view | Requests by status, open requests, and a schedule. |
| Action queue | A prioritised, paginated to-do surface. |
| Activity feed | A live, cross-module record of what's changing. |
| Reminders | What's coming up. |
| Scoped & fast | Respects per-user data scope; built on bounded, efficient queries. |
6Security & performance#
- Per-user data scoping: every figure and list reflects only what the user is entitled to see.
- Built for speed: the dashboard uses single, bounded queries per widget and progressive (deferred) loading, so it stays fast even as data grows.
7Use cases & scenarios#
Use case A — Start the day#
A manager logs in, sees their action queue at the top, three requests due today on the schedule, and the activity feed showing what changed overnight — and knows exactly where to begin.
Use case B — A leader's pulse check#
An owner sets the period to this quarter, glances at KPIs, the revenue trend, and receivables aging, and gets the state of the business in seconds without opening a report.
8Glossary#
| Term | Meaning |
|---|---|
| Action queue | The prioritised list of items needing the user's attention. |
| Receivables aging | A breakdown of outstanding money by how overdue it is. |
| Activity feed | A live, cross-module log of recent changes. |
| Deferred loading | Loading a section on demand so the page appears instantly. |
This document describes the Dashboard as currently built: a personalised, period- and currency-aware command centre with stats, work, and feed bands, scoped per user and loaded progressively.