Auxot
Tutorials Docs Pricing Login

Finish first-run onboarding

Clear Auxot’s welcome wizard at **`/app/onboarding`**: GPU demo key, agents, chat, audit logs, and billing. Finish so your org leaves **registration** state and teammates stop landing on **onboarding-blocked**.

Plus: three Admin Agent assists: owner stuck on a step, a teammate-facing note while registration finishes, and a sanity pass that separates wizard demo keys from a real GPU worker ([Connect a GPU worker](/tutorials/connect-a-gpu-worker)).

Audience Admins · Everyone
Time ~8 min
Prerequisites You are the **organization owner** (only owners complete the wizard; everyone else waits). Fresh org in **onboarding** / incomplete registration, or you’re reading ahead before signup. Helpful: [Say hello to the Admin Agent](/tutorials/say-hello-to-admin-agent) (chat vocabulary), [Take Auxot's pulse in 10 seconds](/tutorials/take-auxots-pulse) (where **System Health** lives).
You'll end up with All five welcome steps finished: **`gpu.`** demo key created or acknowledged, orientation steps marked complete, billing setup understood. Owners reach **`/app`** without a forced redirect.

When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.

Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.

Why this matters

New organizations start in an onboarding registration state. Until the owner finishes the in-app welcome flow:

  • Visiting /app sends the owner to /app/onboarding: headline Welcome to Auxot, five numbered steps.
  • Everyone who isn’t the owner hits /app/onboarding-blocked instead: warning that registration is incomplete and only the owner can finish it.

That split is intentional: GPU keys, billing touches, and first-run orientation shouldn’t scatter across half-invited members before you decide the org is ready.

The wizard steps are:

  1. Create GPU Key: create a gpu.… demo key (shown once: copy before you leave the step).
  2. Introduce Agents: orient to custom agents vs the Admin Agent (Create an agent from scratch comes next when you build deliberately).
  3. Introduce Chat: same surface as Say hello to the Admin Agent.
  4. Audit Logs: aligns with View your audit logs.
  5. Billing Setup: finish commercial registration (copy may reference billing completion before the org fully activates).

Progress persists in this browser (local storage): finishing on another device or after clearing site data may reset the stepper UI even though keys already exist; use the step tiles to navigate back.

Today, you click through as the owner so /app unlocks for you and onboarding-blocked lifts for everyone else. The next time a teammate tries to sign in, they reach a real shell instead of a holding page.

Nothing checks itself off automatically: you click through and you store the gpu. secret safely.

Quick start

  1. Sign in as the org owner: use the account that created the organization.
  2. Open onboarding: go to /app/onboarding, or land there automatically from /app while onboarding is required.
  3. Complete Step 1 (GPU key): use Create Demo GPU Key if you want a throwaway key for the checklist; copy the gpu. value immediately (Connect a GPU worker covers a real machine-backed worker later).
  4. Complete Steps 2–5: read each panel; use Mark Step N Complete (or the step-specific actions) until the wizard reports All Steps Complete.
  5. Confirm teammates can enter: after the owner finishes, members should reach /app normally; if someone still sees onboarding-blocked, the owner hasn’t cleared billing or the org is still in onboarding. Ping the owner; don’t thrash invites (Invite your first teammate).

Done? You (owner) see the main app shell at /app; invitees stop seeing the blocked page.

The agent can do that?

You know why /app splits owners from everyone else, and what the five tiles are for. These three prompts cover a stuck owner, a neutral note for blocked teammates, and the gap between a wizard demo key and production npx @auxot/worker-cli.

1. Owner stuck mid-wizard

Chat → Admin Agent (from another tab if chat is already available, or after partial completion):

I'm on /app/onboarding Step [N]. Symptom: [button gray / error toast / can't advance]. What should I verify first (browser storage, owner session, billing state) before I call it a bug?

Why it’s non-obvious: Failures mix UX state (local progress) with server state (org billing). Paste symptoms; Admin Agent orders checks after you describe what broke.

2. Teammate-facing note while waiting

Draft a two-sentence Slack message explaining onboarding-blocked: owner must finish Auxot registration. Neutral tone, no blame.

Why it’s non-obvious: Blocked users assume “broken invite.” A canned note saves the owner inbox thrash.

3. Demo key vs production GPU path

We clicked Create Demo GPU Key in onboarding. What's the difference versus [Connect a GPU worker](/tutorials/connect-a-gpu-worker) for production? When do we rotate or replace keys?

Why it’s non-obvious: Same gpu. prefix doesn’t mean same ops story: wizard key satisfies checklist; worker-cli plus provider config is the durable path.

Go deeper

Why non-owners are hard-stopped

Billing and legal acceptance belong to the owner identity. Members waiting on /app/onboarding-blocked should see your org name and a Sign Out path: they’re not broken; they’re gated.

Already have a GPU key?

If a demo key row already exists for the org, Step 1 may auto-complete: don’t recreate keys blindly; rotate via Settings if you exposed one accidentally.

Self-hosted stacks

Bring-up still ends in a browser wizard for new orgs (Self-host Auxot stage by stage). Infrastructure Terraform isn’t a substitute for owner orientation unless product defaults change: treat the wizard as a human checklist.

Completion banner vs routing

When every step shows ✓ Complete, you should see an All Steps Complete message referencing billing follow-through. If navigation still loops, refresh once; if it persists, verify billing state with Admin Agent support prompts: stale sessions occasionally need re-login.

Walkthrough

Step 1: Confirm you’re the owner

Non-owners cannot finish this wizard: delegate to the creating account or transfer ownership first.

Step 2: Step 1 (Create GPU Key)

Click Create Demo GPU Key when offered. Copy from the readonly field; heed shown only once warnings. Advance or confirm auto-advance to Step 2.

Step 3: Steps 2–3 (Agents and Chat)

Skim links and copy: these mirror early tutorials (Say hello to the Admin Agent, Create an agent from scratch). Mark complete when you’ve opened Chat once if the panel asks you to.

Step 4: Step 4 (Audit Logs)

Open Audit Logs from the navigation the wizard describes: future forensics live here (View your audit logs).

Step 5: Step 5 (Billing Setup)

Complete pricing and payment flows your tier requires. Until billing satisfies Auxot’s expectations, teammates may remain blocked even if GPU steps look green.

Step 6: Exit check

Browse to /app. Owners should stay; completing onboarding may also redirect automatically from /app/onboarding.

What’s next

Reference

Browse all tutorials