Skip to content

Link your Slack account

This guide shows you how to link your chat identity to your Control Center user and how to unlink one.

Every member does this once per chat provider. It is separate from connecting the app: the connection makes the bot reachable for the whole workspace, the link makes you recognisable inside it.

The bridge refuses to act for a chat account it cannot resolve to a workspace member. That is deliberate — without a link, every message from Slack would have to be attributed to whoever installed the app and the audit trail, per-principal rate limits and ticket reporters would all name the wrong person.

An unlinked member who mentions the bot gets a reply in that Slack thread explaining how to link. Nothing is dispatched.

Linking takes both sides: sending a code from Slack proves the Slack account, and confirming it in Control Center proves that account is yours.

  1. Go to Settings → You → Profile and find the Linked chat accounts card
  2. On the Slack block, click Link my Slack account. The dialog shows a one-time code, for example:
K7M2QP
  1. In Slack, send that code to the bot in a direct message: just the code, nothing else
  2. The bot replies “Got it. Confirm this Slack account in Control Center to finish linking.” and the dialog you left open shows the Slack profile that sent the code: its name and Slack member id
  3. If it is your account, click Confirm. The link is made, the dialog says so and the bot confirms in the same direct message
  4. If it is not yours, click Decline. Nothing is linked and the code stops working; click Get a new code to try again

Closing the dialog does not lose a claim. A code that arrives later waits on the Link my Slack account row of that card, with the same Confirm and Decline.

Why the confirmation step: a code read over your shoulder and sent from somebody else’s Slack account would otherwise make that account act as you. Only you can confirm, and only the exact profile that sent the code.

The code:

  • Is single-use and expires 15 minutes after it is minted
  • Is always minted for you, never for a teammate
  • Works only in a direct message to the bot. In a channel it is just a message
  • Can only be claimed by a full member of the Slack workspace the bot is installed in, not by a guest or someone from another organisation
  • Replaces any code you already hold, so pressing the button again invalidates the previous one
  • Lives in memory only, so a server restart invalidates outstanding codes — press the button again

A code that is unknown, expired, declined or minted for a different workspace fails the same indistinguishable way: “That code is not valid (or has expired).”

If your Slack profile carries a confirmed email that matches the verified email of a Control Center user who is already a member of this workspace, the bridge links you the first time you talk to it. No code needed.

The Control Center side counts as verified when single sign-on or SCIM set the address, or the server owner confirmed it in Settings → Server → People. An address you typed in your own profile is not verified, so it links nothing until the owner confirms it; use the code flow meanwhile.

Both halves matter: the email match proves identity, but only membership grants access, so a stranger whose email happens to exist on the server links to nothing. The roster shows how each link was made (“matched by email” or “linked with a code”).

Automatic linking needs the users:read.email scope. Without it, Slack will not disclose the address and the code flow is the only path.

The roster is workspace administration, so it lives in the admin card: Settings → Workspace → Integrations → Chat bridges → Linked accounts. It lists every linked member in the workspace, with the Slack account each maps to and how the link was made.

Your own state is on Settings → You → Profile: the Link my Slack account row reads “Linked to your-slack-id” once you are linked and tells you to link when you are not.

The roster and the claim are live subscriptions, because the change happens on the other side: you send the code in Slack, so no request from the app can carry the answer back.

Click Unlink on a row in the workspace roster.

  • Anyone can unlink themselves
  • Only an admin can unlink another member
  • Unlinking also revokes any outstanding link code for that member

After unlinking, that Slack account can no longer drive agents until it links again. Existing spaces, transcripts and tickets keep their original attribution — unlinking is not a retraction of past work.

The bot says I am not a member of this workspace

Section titled “The bot says I am not a member of this workspace”

Your Slack account is linked to a Control Center user, but that user holds no membership in this workspace. Ask an admin to invite you; see Multiplayer — identity, membership and presence.

viewer and guest roles cannot start work. An admin has to raise your role to member or above.

The code expired, was already used, was declined, or was replaced by a newer one. Click Link my Slack account again and send the new code.

You sent it in a channel, or your Slack account is already linked. Codes are only taken in a direct message, and a code-shaped message from a linked account is an ordinary request.