Feature
Portal access should feel likethe next scene in the same system.
Login, auth entry, and the first operator handoff are part of the public experience. This rebuild makes them feel designed instead of inherited.
How the handoff works
The public site earns the click. The auth and portal layer should preserve conviction instead of forcing users through a visual reset.
Decide
The public page clarifies whether the user should claim the listing or log in.
Authenticate
Login, magic link, reset, and secure-link handling keep the same brand and page rhythm.
Enter the workspace
Authenticated users continue straight into `/manage` with the existing behavior preserved.
This is where public polish becomes product credibility
If the public site looks premium but auth and portal access feel legacy, the entire system loses trust. The v2 rebuild closes that gap.
No visual whiplash at login
No dead-end utility pages
No disconnect between promise and workspace
Related
See the rest of the operator system
Feature pages should connect into a coherent owner-first narrative instead of leaving operators in isolated detail views.
Related feature
Listing quality that feels
Claim, verify, and tighten the public layer before the rest of the stack scales.
Related feature
Menus that make the visit
Menus should reduce uncertainty and increase visit intent.
Related feature
Promotions that feel
Promotion publishing should sharpen intent, not blur the product boundary.
FAQ
Feature questions
Keep feature pages useful by answering the practical questions that affect operator confidence.
No. It updates the public shell and auth-adjacent experience around those flows, but leaves the new signup and onboarding functionality untouched.
Move from feature detail into the operator flow.
Each feature page should end with a clear next step: claim the dispensary or open the portal.