Flows/Sign in
Valere CRM · Design foundations

Flows

Sign in

Live app layoutIn the app

How a Valere colleague gets into the CRM, screen by screen, in the chosen sign-in layout: the form on the right, the Live app panel on the left. Press the buttons and links on a screen to follow the flow. Nothing is checked or saved here: this is a walk through the screens.

A forgotten password has its own flow: Reset password.

The form, its messages and where each role lands are the app's: SignIn.tsx, components/form.tsx, components/AppShell.tsx. The two halves are the app's too since 2026-10-07: AuthLayout and LiveAppPanel in web/shared/components (Sign-in layouts, ADR-0041). Screens marked Design only are on the design boards but not in the app.

Sign inWhere everyone starts. There is no sign-up: an admin creates each account.
/auth/sign-in
Sign in · nothing enteredChecked in the browser before anything is sent. Each field says what it needs.
/auth/sign-in
Sign in · wrong email or passwordOne message for a wrong password and for an unknown email, so the page never confirms that an account exists.
/auth/sign-in
Signing inThe button is off until the answer comes back, so the form is sent once.
/auth/sign-in
When the answer comes:Signed in
Sign in · too many attempts Design onlyAfter repeated failed attempts sign-in pauses. The same message shows for any email, known or not.
/auth/sign-in
Sign in · session ended Design onlyShown when a session expires or is ended elsewhere. Nothing from the page the user was on stays on screen.
/auth/sign-in
Signed inEveryone lands on their dashboard. Liam Carter holds the Land role, so his is the Individual dashboard. The card at the top of the sidebar shows who is signed in and in which role. The MD, and the admin, land on the Executive dashboard instead; the admin reads everything, changes nothing and has one more menu item, Create staff user.
/dashboard
Individual dashboard · Land

The dashboard's own screens are a later flow on this site. In the app this page shows the tiles Open actions, Overdue, My deals and Needs attention, a card for the role, and the cards My actions, My deals, Deals requiring attention and Exchange forecast.

Who lands where

The six accounts of the demo data. The role decides the dashboard and what the user may change.

AccountRoleLands on
Beth MorganBack OfficeIndividual dashboard
Liam CarterLandIndividual dashboard
Sophie TurnerPartnershipsIndividual dashboard
Dan HughesConstructionIndividual dashboard
Alex ReidMDExecutive dashboard
Demo AdminAdminExecutive dashboard, read only; one more menu item, Create staff user

Behind the screens

Not built yet