First move
Create the org and assign the role.
Booker should know who is operating, what organization they represent, and where they need to land before the rest of the app appears.
Role-aware entry
This entry flow should feel like a guided product kickoff: set the operator, establish the organization, and drop the user into the surface that proves value fastest.
Next destination
Deposits, balances, payouts, and route-level profitability.
First move
Booker should know who is operating, what organization they represent, and where they need to land before the rest of the app appears.
Immediate handoff
Deposits, balances, payouts, and route-level profitability.
Expansion path
Once the core path is clear, the rest of the role-based surfaces should feel discoverable without overwhelming the first session.
Production auth bridge
Alpha users should authenticate through Clerk, then Booker will resolve their role and organization into the app session.
Real alpha access
This alpha uses the Clerk-backed Booker bridge as the default entry path, so internal persona launchers stay out of the way for real testers.
Sign in with your provisioned email and finish the Clerk handoff to land in the correct organization and role. Internal demo launchers remain available only in local/demo environments.
First session checklist
The first session should answer three questions quickly: what Booker is for, why this user is here, and what to do next once they land.
Use the `next` handoff so every entry point feels tailored, not generic.
Personas should show role boundaries without making onboarding feel like a fake sandbox.
Once the first flow clicks, users should naturally branch into the rest of Booker’s operating story.