Dashboard views by role
What each role sees on the main dashboard and why the dashboard is really a routing layer into operational queues.
The dashboard changes by role family
Approval users see pending, approved, and rejected approval queues. Payment officers see ready-for-payment priority stacks. Reject officers see rejected document totals and a working list. Super admins see business-wide summaries.
Cards are linked queues, not vanity KPIs
Each summary card links into a concrete route such as approval status, payment priority, reject approval, or a document family list. The operational meaning is more important than the number itself.
Document family summaries still matter for clients
Clients get document count breakdowns and upload summaries, which makes the dashboard or get-started surface an intake monitor as much as a finance workspace.
Continue with adjacent workflows
Client onboarding and first login flow
How Datamonster decides whether a user lands on Get Started or Dashboard, and what the onboarding checklist actually tracks.
Approval levels and rejection logic
The real two-step approval model in Datamonster, including role separation, counts, pending queues, and reject officer visibility.
Managing ready-for-payment priorities
How payment officers see urgent, medium, low, and unset queues after approvals are complete.