Dashboard

A live snapshot of the work happening across your tenant. The Dashboard is intentionally separate from My Work: My Work is action-oriented, and the Dashboard is observation-oriented. KPIs, focus outlook, module shortcuts, and an activity stream are all driven by the same replica that powers the rest of the app, so it never goes stale.

• KPI strip: open, overdue, due-today, and streaks, all density-aware
• Flow and velocity panel: cycle-time p50/p90, monthly throughput, and a weekly burndown sparkline
• Top-projects rollup: completion rate over the last 14 days
• Density preference is shared with My Work, Tasks, and Board; change it once and every surface follows
• A widget library of module widgets, each offered only where the plan carries its module and the role clears its floor. Client Delivery contributes six: engagement portfolio health, engagements at risk, RAID heat, information requests overdue, actions due, and approvals waiting

• The Dashboard is read-only. Every action (compose task, plan week, triage) deep-links into the corresponding workflow page.
• Tiles fetch from the local replica, not a separate API, so you get the same numbers as My Work with no possibility of drift.

1. 1Open it with `g h` (Linear-style chord) or click Dashboard in the sidebar.
2. 2Tap any KPI tile to drill into the matching list (for example, overdue jumps to /my-work?filter=overdue).
3. 3Set the density toggle in the header to match the rhythm you want across the whole app.

Why is the burndown sparkline showing the wrong number?

The sparkline counts open tasks per day at midnight UTC. If you just closed a batch of tasks, the current bar lags by a render, so refresh to see the new count.

Can I act on something directly from the dashboard?

No, and deliberately. The dashboard is read-only and every control deep-links into the workflow that owns the action, so there is one place where each change is made rather than two.

Do the tiles agree with the numbers elsewhere in Atlas?

Yes. Tiles read the same local replica that My Work reads, rather than a separate reporting endpoint, so the two cannot drift apart.