Verify your org is ready before you invite
Run a short owner checklist so the first human you invite lands in **Chat** instead of **onboarding-blocked**, hits a working model route, and has tutorial links beside the invite link when Auxot does not auto-email.
Plus: three Admin Agent prompts that audit registration, providers, chat identity, and role surprises before you copy the invite link from **Settings → Users**.
| Audience | Admins · Executives |
|---|---|
| Time | ~5 min |
| Prerequisites | You are the org owner or an admin who can invite on Team, Business, or Enterprise ([Invite your first teammate](/tutorials/invite-your-first-teammate) covers the click path and tier rules). Registration is complete enough that teammates should not sit on **onboarding-blocked** ([Finish first-run onboarding](/tutorials/finish-first-run-onboarding)). Helpful: you already ran [Make your first hour in Auxot count](/tutorials/make-your-first-hour-in-auxot-count) so **System Health**, **Chat**, and **Context Files** feel familiar. |
| You'll end up with | A pass-or-fail readiness sweep with written notes for anything deferred, a default bundle of invitee-facing tutorial links to paste beside the invite, and three Admin Agent prompts you can rerun after you change providers or Slack wiring. |
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
Auxot does not email your invite for you. You copy a link from Settings → Users and carry it in Slack, email, or text. That means you are the onboarding experience until they click.
If registration is half-finished, your invitee hits onboarding-blocked and blames themselves. If no model route exists yet, Chat has nothing to answer with on arrival. If Slack matters and Linked Accounts is still empty for real humans, bots stay quiet or refuse to act in ways that look like bad AI instead of missing identity.
This tutorial is the boring gate before the social moment. You are not rehearsing a speech. You are confirming that the basic services (Chat, System Health, providers, identity) actually work before someone clicks an invite link.
Today, you verify the shell, bundle the links you will paste beside the invite, and only then open Invite User. The next time you bring someone new on, the checklist is already waiting.
Free tier orgs cannot invite teammates by design. If you are solo on Free tier, treat this as a read-ahead for upgrade timing (View and manage your License), not as a flow you run today.
Quick start
- Confirm registration state: as the owner, browse to
/appand make sure your org is not still trapping non-owners on onboarding-blocked (Finish first-run onboarding). - Skim System Health: open System Health and spend about sixty seconds on cards and colors (Take Auxot’s pulse in 10 seconds).
- Prove Chat: open Chat, pick the Admin Agent, send
hello, and wait for a streamed reply (Say hello to the Admin Agent). - Check providers and identity: open Settings → Providers and confirm a sane model path exists (Connect a cloud AI model). If your team lives in Slack or Discord this week, open Settings → Linked Accounts for your own user and finish linking before you ask others to (Link your chat apps to your Auxot account).
- Bundle links for the invitee: keep three tabs ready to paste beside the invite link: Accept your invitation and join your organization, Unstick your first week in Auxot, and Find the right screen for your next question. Optional fourth: Make your first hour in Auxot count.
Done? You would happily click your own invite link in a fresh browser profile, and your welcome message names what is already wired instead of asking the new person to invent the org from scratch.
The agent can do that?
You already clicked the checklist once. These three prompts ask the Admin Agent to audit what you might have missed before you copy the invite. Paste them in Chat → Admin Agent.
1. Run a ten-line readiness audit
I am about to invite my first teammate on a paid team plan. From what you can infer about this org, output a numbered readiness checklist (max ten items) covering registration state, model routes, agents or an explicit note if none exist yet, context files, Slack or Discord identity risks, and license headroom. Mark each line pass, fail, or unknown. For every unknown, name the exact Settings or left-menu page I should open to resolve it.
Why it’s non-obvious: Humans forget what they skipped last Tuesday. A table forces unknown into the open before someone else discovers it at midnight.
2. Stress-test chat apps before non-technical invitees arrive
Our team coordinates in Slack or Discord daily. Before I send invite links to non-technical people, what should already be true in **Settings → Linked Accounts** and in workspace bot wiring so mentions do not turn into silent skips or anonymous reactions? Bullet list only, max six lines, each line starts with an action I can verify in the UI.
Why it’s non-obvious: Workspace-level connection is not the same thing as each human linking identity. The failure looks like the agent ignores them or refuses to act on their messages when it is actually Auxot does not know which human spoke.
3. Preview the User role surprise list
I plan to grant org role User (not Admin) to my first invitee. List five capabilities they will expect but will not have. For each, give the symptom they will see in the UI and one neutral sentence I can paste into my welcome email so they do not assume the product is broken.
Why it’s non-obvious: Most first invites should be User. Without language up front, new people assume they can change providers or billing, hit a wall, and file noise.
Go deeper
Free tier and solo orgs
Free tier accounts are solo by design. You cannot run this checklist for invites until you upgrade to a team-capable plan. Use the time to improve Context Files and Chat anyway, then return when billing matches your intent (View and manage your License).
When to wait on invites even if the checklist is green
Delay the invite if you are mid-provider outage, mid-credential rotation, or mid-license change you cannot explain in one paragraph. A stable hour beats an early invite that trains the team to ignore Auxot notifications.
Invite link logistics (seven days)
Invite links expire after about seven days. If your human is traveling or on leave, either wait to generate the link or plan to reissue one (Invite your first teammate). Your readiness work still counts; only the invite token needs reissuing.
Walkthrough
Step 1: Owner session on /app
Sign in as the person who can finish registration. Browse to /app. If you still bounce to /app/onboarding, finish the wizard before you invite anyone else.
Step 2: Read System Health before you invite anyone
Open System Health. You are not chasing every yellow card before the invite. You are deciding whether right now is a bad day to ask a human to log in for the first time.
Step 3: Chat smoke test
Open Chat, pick the Admin Agent, send hello. No stream means you stop the invite plan and fix the model path first.
Step 4: Providers and Linked Accounts
Open Settings → Providers and confirm at least one path matches what you tell new hires verbally (we use Claude through Auxot, we route to our GPU, and so on).
If Slack or Discord is part of how this person will meet Auxot, open Settings → Linked Accounts under your own login and finish linking. You are modeling the behavior you will ask them to repeat.
Step 5: Write the paste block once
In your notes app, draft four lines: the invite link placeholder, then one sentence each for Accept invitation, Unstick, Find the right screen, and optional First hour links from the Quick start list. When the modal gives you the URL, paste it into your template and send.
What’s next
- → Invite your first teammate. When the checklist is green and you are ready to click Invite User on Settings → Users.
- → Choose your day-two track in Auxot. Single-thread your own week two while invites and Linked Accounts catch up, so you are not reopening every menu while onboarding others.
- → Accept your invitation and join your organization. So you can read the invitee flow you are about to put someone through.
- → Link your chat apps to your Auxot account. When chat identity is still the riskiest unknown.
- → Create an agent from scratch. When you want the second human to land in something other than an empty agent list.
- → Onboard a new teammate to your agents. When you already run several agents in production and need a structured live session after they accept.
Reference
- Invite creation: Settings → Users (Invite your first teammate)
- Invitee activation: Accept Invitation public flow (Accept your invitation and join your organization)
- See also: Make your first hour in Auxot count, Choose your day-two track in Auxot, Find the right screen for your next question, Connect Discord to your agents, Unstick your first week in Auxot, Finish first-run onboarding