Routes
/dashboardFlow 6
Dashboard Lifecycle
The dashboard answers one question: what should I do next with my documents?
1
Routes
6
Buttons
2
Screenshots
3
Watch-outs
ELI10
The dashboard answers one question: what should I do next with my documents?
W5
Who: signed-in users managing documents over time.
What: active work, saved copies, signing status, signed PDFs, audit proof, archive, templates, notifications, usage.
When: after upload, save online, send, sign, archive, or reuse.
Where: /dashboard.
Why: SaaS value comes from keeping the whole document lifecycle organized.
Flow graph
Screens and paths in this flow
Each step connects to its screen manual. Follow the nodes left-to-right to trace the document journey.
4nodes
Step 1DashboardActive documents, proof vault, templates, and archive.
Dashboard Lifecycle1 route · 6 actions
Dashboard
Important buttons
Watch-outs
The screenshots are captured from the seeded Help Hub test account, so they show the actual signed-in dashboard and status room.
The dashboard should avoid card-inside-card nesting and excessive bright CTAs.
Documents without recipients should be treated as private saved copies, not broken signing packages.