Accept your invitation and join your organization

Use the invite link your admin sent, set a strong password on **Accept Invitation**, sign in, and know what to do if the org is still finishing first-run onboarding.

Plus: three Admin Agent prompts after you sign in: a first-week checklist from what is already wired, a polite ping for a stuck owner, and a blunt read on whether your role matches how you will work.

Audience	Everyone
Time	~5 min
Prerequisites	A valid invitation link from someone who already invited you ([Invite your first teammate](/tutorials/invite-your-first-teammate)). They generate the link from Settings → Users. The link is time-limited (seven days in normal setups). You can complete this flow on a laptop or desktop browser.
You'll end up with	Password set on Accept Invitation, account activated, and first successful sign-in to the right org. You also know why onboarding-blocked appears and who has to clear it.

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

Your admin copied an invitation link instead of hoping Auxot would email it for them. That link is the proof of which org you belong to and which email the invite was issued for. Until you finish Accept Invitation, you do not have a usable password, your email is not treated as verified for that flow, and your membership stays in a pending state.

Today, click the link, set your password, and land in the org they prepared. The next time you open Auxot, you are in Chat, Linked Accounts, and the same agents your team already tuned, not a blank solo trial.

Accepting verifies your email for this activation path, sets your password, and records invitation acceptance on pending memberships so Auxot can enforce the role your admin picked.

Quick start

Open the invitation link: use the URL your admin sent (same device is fine; copying into a fresh browser tab is OK). If the page title reads Invalid Invitation, the token is missing, expired, or already used. Ask for a fresh invite (Invite your first teammate).
Read the card title: a valid link shows Set your password and explains that you are activating access to your organization.
Enter and confirm a password: at least 12 characters in both fields. They must match. The form labels read Password (Min 12 characters) and Confirm Password (Min 12 characters).
Click Activate account: the server sets your password, verifies your email if needed, marks the invite token as used, and redirects you to Sign in with an invitation success hint in the URL.
Sign in with the invited email: use the same address your admin typed on the invite form and the password you just set.

Done? You reach the main app shell, or you see an onboarding gate that names your org and tells you the owner still has steps to finish (see Go deeper).

The agent can do that?

You are past the gate and signed in. If you still see onboarding-blocked, jump to Go deeper first. Once Chat is available with the Admin Agent, these three prompts match the rhythm from Say hello to the Admin Agent.

1. Turn visible setup into a first-week checklist

Chat → Admin Agent:

I just joined this org through an invite. Looking at what you can infer about our agents, teams, and connected pieces, list a sensible first-week checklist for me as a new member. Order it day-by-day, keep it to six bullets max, and call out anything that looks risky or admin-only so I do not step on permissions I should not touch.

Why it’s non-obvious: New members guess what to click. One paste anchors you to what is already configured instead of a generic productivity blog.

2. Draft a polite nudge when the owner is blocking onboarding

Chat → Admin Agent (only if you are already inside the product shell but teammates still cannot enter Chat):

Draft a short DM or email I can send to our Auxot org owner explaining that teammates are stuck on onboarding-blocked until the owner finishes first-run steps. Neutral tone, no blame, three sentences max, and mention they should check [Finish first-run onboarding](/tutorials/finish-first-run-onboarding) if they want the checklist.

Why it’s non-obvious: Blocked teammates assume the invite failed. A calm note saves everyone from revoking invites that were fine.

3. Ask whether your assigned role matches reality

Chat → Admin Agent:

Here is the org role and (if shown) team role I was given when I accepted my invite: [paste what you see under Settings → Users or your profile]. Given how I described my job in two sentences ([your two sentences]), is this role too much, too little, or about right? Be blunt and say what I should ask an admin to change if it is wrong.

Why it’s non-obvious: Invites default to broad roles when admins are in a hurry. A second opinion before you build habits on the wrong permissions beats a later permissions incident.

Go deeper

Why you land on Sign in after activation

The Accept Invitation page only collects passwords. After a successful activation, Auxot redirects you to Sign in so you establish a normal session. Use the invited email address and the password you just created.

If you see onboarding-blocked

The org owner has not finished first-run registration steps (GPU demo key orientation, billing acceptance where required, and the rest of the welcome checklist). Non-owners are hard-stopped on purpose so billing and legal touches stay with the owner. Send the owner to Finish first-run onboarding and wait for the all-clear. You are not broken; you are gated.

If you already had an Auxot login

Use Sign in on the activation redirect instead of trying to create a second account. The invite is bound to the email your admin entered.

Troubleshooting

Invalid Invitation: token missing, wrong link, seven-day expiry, or the invite was already consumed. Ask your admin to revoke and recreate from Active Invites if needed (Invite your first teammate).
Password must be at least 12 characters: both fields need matching passwords that meet the minimum.
Passwords do not match: retype carefully; password managers sometimes autofill the wrong field.
Activate account spins then errors: network hiccup or server rejection. Read the red inline alert, try once more, then ask your admin to confirm the invite is still pending.
Signed in but agents ignore me in Slack or Discord: complete Settings → Linked Accounts (Link your chat apps to your Auxot account). Bots only know which human you are after you link yourself.

Variations & edge cases

Business or Enterprise team placement: your admin picked a team and team role during invite creation. If resources look empty, you might be on the wrong team; ask an admin to verify membership (Invite your first teammate, Set up multi-team isolation).
You need a password reset later: use the normal forgot-password flow from Sign in; that is separate from invitation tokens.

Walkthrough

Step 1: Open the invitation URL

Click the link from your admin. Expect either Set your password (good) or Invalid Invitation (bad). Copy the full URL if your mail client wrapped lines.

Step 2: Set password fields

Enter a password twice. Minimum length is twelve characters. The page shows Password (Min 12 characters) and Confirm Password (Min 12 characters).

Step 3: Activate account

Click Activate account. Wait for the redirect to Sign in. If an error banner appears, read it literally (length, mismatch, expired token).

Use the invited email and the password you set. If your organization enforces additional checks, complete them as prompted.

Open Chat and pick the Admin Agent if you want orientation help (Say hello to the Admin Agent). If Slack or Discord is part of your workflow, plan Settings → Linked Accounts next (Link your chat apps to your Auxot account).

What’s next

→ Say hello to the Admin Agent. Vocabulary for Chat once you are inside the org.
→ Pick the right model for the job. Once Settings → Providers is visible to you, compare models before every agent inherits the org default.
→ Unstick your first week in Auxot. When you are signed in but something still feels wrong, you get a map of the usual first-week gates.
→ Link your chat apps to your Auxot account. So Slack and Discord stop ignoring you once you link your identity.
→ Finish first-run onboarding. If you are the owner finishing the wizard, or you need the checklist to send upstream.

Reference

Public pages: Accept Invitation (password activation), Sign in
Admin-side invite creation: Settings → Users (Invite your first teammate)
See also: Invite your first teammate, Finish first-run onboarding, Pick the right model for the job