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.
Landing behavior is role-driven
The root page does not act as a dashboard. It fetches the signed-in profile first, then redirects CLIENT users to `/get-started` and other roles to `/dashboard`.
That means the knowledge base should teach two entry experiences: guided setup for clients and operational monitoring for approval, payment, reject, or super admin roles.
The onboarding checklist is explicit in the code
The Get Started page tracks a small set of personal todo flags rather than an inferred progress percentage.
- Upload documents: `upload_from_device`
- Review and export: `review_document`, `export_document`
- Chat with documents: `prompt_document`
Subscription context is surfaced early
The onboarding view also shows monthly extraction usage, package renewal timing, and a direct Add Document action when usage is still available.
Operationally, this means first-time guidance should connect upload behavior to package limits, not treat uploads as unlimited.
Continue with adjacent workflows
Uploading and classifying documents
What happens when a file is added, how business scoping works, and where the five document types appear across the product.
Using the AI prompt workspace
What the in-product prompt assistant can do, how sessions are stored, and why exports are part of the chat workflow.
Dashboard views by role
What each role sees on the main dashboard and why the dashboard is really a routing layer into operational queues.