Link your chat apps to your Auxot account

Finish **Settings → Linked Accounts** once so Slack and Discord bots know which Auxot user you are, tools stay scoped correctly, and mentions in channels stop coming back as a 🙈 reaction.

Plus: three pasted asks: teammate-facing announcement drafted from Admin Agent, Discord DM privacy triage ordered, and a manager checklist when half the team still cannot see the bot.

Audience	Everyone · Admins
Time	~5 min
Prerequisites	An Auxot login. Your org already has Slack and/or Discord wired to agents ([Connect Slack to your agents](/tutorials/connect-slack-to-your-agents), [Connect Discord to your agents](/tutorials/connect-discord-to-your-agents); admins do that part). For Discord linking: ability to change per-server DM privacy (Walkthrough). You only link your own identity (no admin permission required).
You'll end up with	Slack and/or Discord showing Linked next to your identity, plus confidence that mentions and DMs route with verified Auxot user context instead of silent skips or 🙈.

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

Admins connect bots to channels. You connect yourself.

Until Settings → Linked Accounts shows Slack or Discord as linked, Auxot can’t tell which person is sending each message. Agents may skip replying, add a 🙈 reaction on mentions-only surfaces, or refuse tools that require knowing which human asked (Slack Integration, Discord Integration).

Linking is self-service and org-wide: one completion covers every Slack bot and Discord bot your organization runs. You still click Send Code and finish verification; nothing links itself because someone invited you to a channel.

Today, you verify once per app you use so mentions and DMs carry you, not a stranger. The next time half the team asks why the bot “ignored” them, you point at Linked Accounts before you debug channel bindings or models.

Admins connect the bot to channels; each person links their own Slack or Discord identity once so the agent knows who is asking.

Quick start

Sign in to Auxot: use your own browser session (not a teammate’s).
Open Linked Accounts: go to Settings → Linked Accounts (sidebar label is exact: “Linked Accounts,” not a generic Integrations heading for this flow).
Pick Slack or Discord: start with whichever app you actually use in channels.
Slack path: click Link My Slack Account → choose the workspace integration → enter your display name exactly as Slack shows → Send Code → open the bot DM → reply with VERIFY <code> (example: VERIFY ABC123).
Discord path: enable Allow direct messages from server members for the guild (Privacy Settings on the server) → Link My Discord Account → enter your Discord username → Send Code → copy the code from the bot DM → paste into Auxot → Verify.

Done? The card shows Linked; an @mention or DM smoke test reaches the agent instead of coming back as a 🙈 reaction.

The agent can do that?

Admins already wired the bots; your job is identity. These three prompts cover rollout comms, Discord privacy triage when verify stalls, and a manager sweep when “the bot is broken” usually means “not linked yet.”

1. Draft the “why link?” note for `#announcements`

Chat → Admin Agent:

We're rolling Auxot bots into Slack/Discord. Draft a short post telling teammates to open Auxot → Settings → Linked Accounts. Explain 🙈 means "not linked yet." List Slack VERIFY-in-DM vs Discord paste-code-in-Auxot in plain bullets.

Why it’s non-obvious: People blame “broken AI” when identity never finished: paste once, edit tone, you still post it.

2. Discord DM privacy ordered checklist

Paste into Admin Agent after a failed Discord verify:

Discord linking stuck after Send Code. User shares server with bot; bot online. Symptom: [no DM / DM but verify fails]. Walk checklist: privacy settings, multiple bots, stale code. Order by likelihood.

Why it’s non-obvious: Discord hides DMs behind per-server toggles separate from global privacy: doc detail easy to miss (Discord Integration).

3. Manager sweep: who still shows 🙈

Half my team claims the bot ignores them. Give me a five-bullet rollout checklist: Linked Accounts first, then channel bindings, then escalation owner. Everything reader-initiated; no “the bot fixes itself” framing.

Why it’s non-obvious: When some teammates have linked and others haven’t, the bot looks broken. A short checklist tells you which step is missing for which person.

Go deeper

Slack vs Discord verification shape

App	Where the proof lands
Slack	You reply in Slack DM with `VERIFY <code>`
Discord	You paste the code back into Auxot’s web UI

Swap them and neither side completes: teach teammates the shape their app uses.

🙈 and silent skips

Slack mentions-only: 🙈 marks unlinked mentions so channels stay quiet.
Slack all-messages: unlinked traffic is silently skipped (Slack Integration).
Discord mentions: 🙈 signals link gap; DMs point people at Linked Accounts (Discord Integration).

Troubleshooting

No Slack DM: bot missing im:write, workspace blocks unsolicited bot DMs, or display name typo vs Slack roster.
Discord verify loop: flip server Privacy Settings → allow DMs from members; multiple bots need separate DM threads.
Stale codes: click Resend or restart the flow; old pending codes invalidate.
Tools still blocked after link: confirm same Auxot org as the bot integration; admins may revoke identities (re-link if that happened).

Walkthrough

Step 1: Confirm integrations exist

If admins haven’t wired Slack or Discord yet, linking still completes but bots have nowhere to talk: finish Connect Slack to your agents or Connect Discord to your agents first.

Step 2: Slack linking

Open Settings → Linked Accounts → Link My Slack Account.
Pick the integration that matches your workspace.
Enter your Slack display name carefully: case and spacing matter for lookup.
Click Send Code. Open the bot DM and reply exactly in the pattern the message shows (for example VERIFY ABC123).

Step 3: Discord prerequisites

Right-click the server icon → Privacy Settings → turn on Allow direct messages from server members. Without it, the verification bot may not be able to DM you a code (Discord Integration).

Step 4: Discord linking

Settings → Linked Accounts → Link My Discord Account.
Enter the Discord username Auxot asks for (same idea as the manual’s linking steps).
Send Code → read the bot DM → paste the code into Linked Accounts → Verify.

Step 5: Prove it

In a bound channel, @-mention the bot (or use your team’s Discord equivalent). Expect a threaded reply, not only emoji feedback.

What’s next

→ Connect Discord to your agents. Admin-side bot wiring after everyone knows the Linked Accounts cheat sheet: intents, guild install, channel bindings.
→ Connect Slack to your agents. Same idea for Slack-heavy teams: bot token and channel modes once members are linked.
→ Connect OAuth for MCP tools. Settings → Connected Accounts when MCP policies use oauth: a separate page from Linked Accounts here.
→ View your audit logs. When you need receipts that requests carried verified identity.

Reference

Pages in Auxot: Settings → Linked Accounts
Manual: Slack Integration (linking section), Discord Integration (linking section)
See also: Customize your Profile, Finish first-run onboarding, Connect OAuth for MCP tools (Connected Accounts vs Linked Accounts), Define a tool policy (tool access still respects identity), Manage your Credentials