Account onboarding

Workspace creation establishes a real Account boundary before any context is acquired. The remaining steps stay in the standalone onboarding flow; the platform's existing Set up workspace is unchanged. Progress comes from committed Sources, explicit grants, and successful query receipts rather than button clicks.

1. Create the workspace

Enter the company workspace name. Combined provisions the Account and its WorkOS organization. The Account is the tenant, authorization, billing, retention, and query-budget boundary. A customer deployment does not expose separate product-level “environments”; production, staging, and personal stages are infrastructure choices, while customer data always belongs to an Account.

Free allowance and optional card

Every Account can connect Sources and commit up to 5 million monthly active records (MAR) without a card. Adding a payment card through Stripe unlocks another 20 million free MAR and starts the seven-day card-backed trial. Combined never receives card details. After the trial, usage is priced at $5 per million MAR, prorated, with no public base charge or minimum. Account-specific commercial terms can override the displayed defaults.

If payment needs attention, the application displays a banner and directs an Owner to Billing. Lapsed Accounts retain structured data only for their configured recovery window before deletion.

2. Connect context

Onboarding uses the same connector catalogue and setup dialog as Connected Apps. Desktop is pinned, but no SaaS connector is hard-wired:

1. choose a Ready connector or request Preview access;
2. connect it yourself or request authorization from the right person;
3. complete the identity-bound authorization flow;
4. select discovered datasets and fields;
5. choose manual, daily, or allowlisted hourly sync;
6. watch the first Run stage and commit deterministic Deliveries.

An authorization request owned by another person never blocks the whole setup workspace. Connect a different Source while the request remains pending.

The flow never treats catalogue presence as production readiness. If a connector is still evidence- gated, the UI records interest without collecting credentials.

3. See the data

Grant yourself the selected datasets explicitly, then open the real Explore table editor. The first successful preview or SQL query writes a receipt and completes this milestone. Suggested questions are query shortcuts inside Explore rather than a separate summary screen.

4. Use it with AI

The default action copies a coding-agent prompt containing the Account-scoped MCP endpoint and safe discovery instructions. OAuth discovery is preferred. Manual MCP, SDK, and scoped WorkOS token setup remain available behind Set up manually. Onboarding completes only after an agent identity runs a successful bounded query and produces a real receipt.

If onboarding stops

• A Source awaiting a person stays in needs authorization until the request completes or expires.
• Discovery or the first sync can be resumed from the Source flow without creating a duplicate Source.
• Cardless setup remains available until the 5M MAR allowance is used.
• Stripe completion may take a short time to reconcile before the additional 20M MAR appears.
• A connector that is not Ready cannot bypass its evidence gate or consume trial MAR.

See Source troubleshooting for recovery steps.