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.
Alpha onboardingPLG handoff
Role-aware entry
Start Booker and land in the right workspace on the first try.
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.
Guided alpha setupDirect workspace landingRole-aware shellClerk-backed staging access
Next destination
Venues
Venue, room, and contact records with provenance.
EnterConfigureOperate
Immediate handoff
Land in Venues.
Venue, room, and contact records with provenance.
Expansion path
Use personas to explore adjacent workflows.
Once the core path is clear, the rest of the role-based surfaces should feel discoverable without overwhelming the first session.
Production auth bridge
Sign in with your real Booker identity
Alpha users should authenticate through Clerk, then Booker will resolve their role and organization into the app session.
Real alpha access
Demo personas are hidden in staging
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.
Use your real Booker identity
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
What a product marketer wants the user to feel
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.
01Immediate relevance
Use the `next` handoff so every entry point feels tailored, not generic.
02Believable product depth
Personas should show role boundaries without making onboarding feel like a fake sandbox.
03Confident expansion
Once the first flow clicks, users should naturally branch into the rest of Booker’s operating story.