Linking your Slack or Teams account
Link your Slack or Teams identity to your QuantumOps account so Qubit can use your tools, sources and routines, and check the link with status.
Written By Chris Scaminaci
Last updated About 3 hours ago
Linking connects your Slack or Teams identity to your QuantumOps account. Until you link, Qubit does not know who you are in QuantumOps, so it answers without tools. Once you link, Qubit can use your tools and your own connections, run your routines, and act on buttons that need to know which agent you are. Anyone who uses Qubit in Slack or Teams can link, whatever their QuantumOps role; you need a QuantumOps sign-in, and every signed-in user can open the link page.
Before you start: Qubit must be switched on for your Slack workspace or Teams tenant (Channel Assistant settings). Qubit only issues link codes while it is on.
What linking changes
Link your account with a code
- Open your direct message with Qubit (Slack) or your personal chat with the bot (Teams).
- Type
link. Qubit replies with a link and an 8-character one-time code. - Open the link while you are signed in to QuantumOps. The code is already filled in. If you would rather type it, open Configuration → Link Slack / Teams in QuantumOps and type the code in Link code.
- Select Link account. The page says Linked your Slack account. Qubit can now use your connected tools. (it says Teams if you linked in Teams).
In Slack you can also type /qubit link in any conversation, or mention Qubit with link in a channel. Slack shows the reply only to you. In a Teams channel or group chat, link does not give you a code. Qubit tells you to send it a direct message instead, because a message in a channel can be read by everyone there.
About the code:
- It has 8 letters and digits. It never uses 0, O, 1 or I, so it stays readable when you type it from a phone. Type the 8 characters without spaces or hyphens; the case does not matter.
- It works once and expires after 15 minutes. Type
linkagain for a new code; the new code replaces the old one. - Qubit sends it only privately: in your direct message, or as a Slack reply only you can see.
- After five wrong codes, the page answers That code is not valid to every code for about 15 minutes, even a correct one. Wait, then try again.
- An expired code gives That code has expired. Ask Qubit for a new one with
/qubit link.
The link page needs a usable sign-in. If your session has no usable identity, the page tells you to sign out and back in, and the Link account button stays off until you do.
Re-link, or link in both Slack and Teams
One QuantumOps account links to one chat identity in each Slack workspace and each Teams tenant. If you link a new identity in the same workspace, the older link to your account is removed. You can still be linked in Slack and in Teams at the same time.
If you type link while you are already linked, Qubit tells you which account you are linked to and suggests status. To move your chat identity to a different QuantumOps account, ask an Administrator to unlink you on the Channel Assistant page, then link again with a code.
Automatic linking from the agent mapping
Your Administrator can map your Slack user or Teams user to your agent record on Configuration → Q-Director Config → Messaging, or with Slack ID and Teams ID under Edit details in Team Management (see Q-Director: Slack, Teams and agent mapping). Qubit then links you on your first message, without a code. It links you only when all of this holds:
- exactly one active agent carries your Slack ID or Teams user, and the Administrator has not excluded that agent from the mapping;
- you have signed in to QuantumOps at least once;
- you message from your organisation's own Slack workspace or consented Microsoft 365 tenant. A Slack Connect user or an outside guest is never linked this way;
- no other chat identity in the same workspace is already linked to your account.
This kind of link gives you the shared tools only. It does not give you your own connections. status tells you which kind of link you have, and type link to add your own. Qubit checks the mapping again on every message and before each routine run, and the link goes away when the mapping no longer holds. An Administrator can switch automatic linking off for one person on the Channel Assistant page.
Shared and per-person sources
Qubit reaches other systems through sources (MCP sources). A source is one of two kinds:
- A shared source uses one connection that your organisation set up (the Tenant: everyone shares one credential scope on the MCP Sources page), and it works for everyone Qubit may serve.
- A per-person source uses your own sign-in, so the other system sees you and not a shared account (the Per user scope on the MCP Sources page). StackJack is an example.
A per-person source needs two things: a link made with a code (an automatic link is not enough), and your own connection under Configuration → MCP Sources. When a source is not ready for you, Qubit adds a line under the answer:
- Type
linkto use your own StackJack connection here. Link with a code in your direct message with Qubit. - StackJack isn't connected for you. Connect it at the MCP Sources page, then ask again. Open MCP Sources in QuantumOps, connect it, and ask again.
Your Administrator can limit which sources Qubit may use in each of Slack and Teams. A source that only you use (the Only me (a personal source) scope) works here too once you have linked with a code, unless your Administrator has limited the sources for the channel.
Check your link with status
Type status in your direct message with Qubit, or after a mention. It shows:
- whether you are linked, as whom, and whether through your own code or the agent mapping;
- the model the channel uses by default, or your organisation's default when none is set (your Administrator chooses both; see Choose the model);
- whether tools are on (Tools: enabled) or off until you link;
- each source Qubit may use for you, marked shared or per person, with its state.
MCP sources: none configured means your organisation has not made any source available to Qubit in this channel.
Related pages
- Qubit in Slack and Teams: how to ask Qubit.
- Commands and private answers:
statusand the other commands. - MCP sources: connect your own sources.
- Channel Assistant settings: the settings your Administrator controls.
- Q-Director: Slack, Teams and agent mapping: the mapping behind automatic linking.
Was this helpful?
Still need help? Ask the team