The End-User Experience
What your users see - passwordless sign-in, starting on a free plan, pricing, credits, and top-ups.
The end-user experience
Beta
The sign-in and purchase surfaces described here ship with Portals and Storefronts, currently in beta.
This page walks the journey from your end user's side, so you know exactly what you're putting in front of customers.
Signing in
Sign-in is passwordless: the user enters their email on your branded login screen and receives a 6-digit one-time code (from your Portal's branded sender). Entering the code signs them in - first time creates the account, every later time returns them to their history, plans, and credits. One identity per email across your organization. A Portal embedded behind your own customer login can skip the code entirely with signed sign-in.
Starting on a free plan
Every visitor signs in before using anything; there is no anonymous mode. When the Portal has a Storefront attached, a new sign-up is placed on the Storefront's default $0 plan the moment their email is verified, with that plan's full credit allowance. Without a $0 default they pick a plan first. Upgrading to a paid plan happens against the same signed-in identity, so history, conversations, and usage carry over.
Pricing and checkout
When a user needs a plan (or picks one), they see the pricing screen - the displayed Storefront's offers with names, prices, trials, and credit allowances. Paid checkout opens Stripe Checkout in a new tab (checkout can't run inside an embedded iframe); when payment completes, access activates automatically. Buyers who arrive from a Storefront embedded on your own site go through the same checkout and are sent to the Portal named on the Storefront afterwards.
Living with credits
Signed-in users see a subscription bar in the experience:
- Current plan, renewal or cancellation state, and a credit meter.
- A soft warning at roughly 70% consumed; a hard stop at exhaustion with an upgrade path. A user on several plans draws from them in turn and is only stopped when every pool is empty.
- Credit packs (when you offer them) - one-time top-ups whose credits survive the monthly reset and burn only after the allowance is used.
- Manage subscription - plan changes and cancellation through the Stripe-hosted portal.
- Their own API key (BYOK plans) - users on a BYOK-enabled plan can add their own OpenAI key so those runs don't consume credits.
Their data
Conversation history, personalization answers, and any private notebook content belong to the end-user identity and follow it across the Portals and Suites you've given them access to - scoped to your organization only.