Channel Assistant settings

The Channel Assistant page, headed Qubit in Slack & Teams, is where an Administrator decides whether Qubit answers in Slack and Microsoft Teams, and how. Each channel has its own card. Below the cards you can see every routine Qubit runs and every chat user it has met.

Before you start:

• Only people with the Administrator role can open this page. Anyone else who opens its address gets the Access Denied screen, and the sidebar does not show them the Channel Assistant link. Linking your own chat account is a different page, open to everyone who is signed in: Configuration → Link Slack / Teams. See Linking your Slack or Teams account.
• Open the page from Configuration → Channel Assistant.
• The Slack app or the Teams bot must already be set up. See Setting up the Slack app and Setting up the Teams bot.

What people see while a channel is off

Qubit is off in each channel until you turn it on, and while it is off Qubit calls no tools.

• Slack: mentions, direct messages, /qubit and the Ask Qubit message shortcut answer "The Qubit assistant is not enabled for this workspace." The older /qops command shows its classic command list instead.
• Teams: messages to the bot are answered by the classic commands, such as help, lunch and status.
• Routines: a routine that comes due is skipped, and its last status says so.

See Agent status commands for the classic commands.

Turn Qubit on for a channel

1. Open Configuration → Channel Assistant.
2. On the Slack or Teams card, tick the box named "Enable the Qubit assistant in Slack" or "Enable the Qubit assistant in Teams".
3. Choose the other settings below, then select the Save button on that card (it is named "Save Slack" or "Save Teams"). A message such as "Slack settings saved." confirms it.

Each card saves on its own, so saving Slack does not save Teams.

A pill next to the channel name shows where things stand:

Choose the model

The Model list sets which AI model the channel uses. The first choice, "Tenant default (Channel Assistant category → Primary model)", follows the model set for the Channel Assistant category in your AI settings. The other choices are the active models of your providers, shown as the model name and its provider. See AI providers and models.

Decide what unlinked people can do

Unlinked users get read-only answers is on by default. While it is on, people who have not linked their QuantumOps account get answers without any tools. Someone whose Slack or Teams ID is mapped to an agent on Configuration → Q-Director Config → Messaging counts as linked for the shared tools. Turn the option off only if you want unlinked people to use tools too.

Send Q-Notice cards to a channel

Under Q-Notice cards, Destination is where Qubit posts Q-Notices as cards with buttons: Acknowledge, Assign to me, Open in Halo and Snooze.

• For Slack, enter a channel ID, for example C0123ABCD. Slack shows a channel's ID in the channel's details.
• For Teams, enter a conversation ID. The conversation must be one where Qubit has been mentioned at least once.
• The destination is also the default for Q-Notice auto rules whose Slack or Teams channel has no destination of its own.
• Leave Destination empty to keep using the incoming webhook, which posts links only.

Include action buttons on Q-Notice cards is on by default. Turn it off to post the cards without the buttons. See How Q-Notices are delivered.

Limit which MCP sources a channel can use

The list "MCP sources available in" Slack or Teams shows every source you can assign, with its name and short alias:

• Shared: one tenant connection for everyone sources use one connection for the whole organisation. This is the Tenant: everyone shares one credential scope on the MCP Sources page.
• Per person: each user connects their own account sources run as each person's own connection. This is the Per user scope on the MCP Sources page. The list says how many people have connected it.

Leave every box unticked to allow all sources. As soon as you tick any, the channel can use only the ticked ones, per-person sources included. A per-person source works only for people who linked their account with a code and connected it themselves. If you have no sources yet, the list says to add them under MCP Sources. See MCP sources.

A source that one person added only for themselves (the Only me (a personal source) scope) is not in this list, because an Administrator cannot see or assign it. It works in Slack and Teams only for its owner, once the owner has linked with a code, and only while every box here is unticked. As soon as you tick any source, personal sources are left out.

Start Teams admin consent

The Teams card has a Grant admin consent (Entra) button. It opens Microsoft's consent page in a new tab and needs a Microsoft 365 administrator. Consent is what lets QuantumOps list your Teams users and link people automatically. The full steps are in Setting up the Teams bot.

Use the setup reference

Each card ends with a Setup reference for the app you configure on the other side:

• Slack: the addresses for Events, Interactivity and Slash command /qubit, and the Scopes the bot needs. The scope list does not include files:read and files:write, which file handling needs. See Setting up the Slack app. The bot token and signing secret are stored on the Messaging tab.
• Teams: the Messaging endpoint, and the App type the bot is registered as. The app type is set up for you.

Review routines

Routines lists every routine in your organisation, across Slack and Teams. People create routines in chat, never on this page; the page shows the commands they use under On a schedule and On an event. Event routines, which run when a HaloPSA ticket changes or a Q-Notice rule fires, are available when enabled for your organisation. See Routines.

The status of the last run is "ok" after a normal run. A status that starts "skipped:" says why Qubit did not run it: the assistant was off for that channel, or the person who created the routine has unlinked their account. A routine runs as the person who created it, so it stays skipped until they link again or you remove it. A status that starts "error:" gives the reason a run failed. Long statuses are cut short. With no routines, the section says "No routines yet."

Manage linked channel users

Linked channel users lists the Slack and Teams people Qubit has seen, newest first, up to the 500 most recently seen. Until someone talks to Qubit, it says "Nobody has talked to Qubit yet."

Two buttons manage a person's link:

• Unlink removes the link. It also stops the agent mapping from linking that person again, so the next message does not link them straight back. They can still link themselves with a code.
• Allow auto-link lifts that block. The agent mapping can link them again on their next message.

Related pages

• Qubit in Slack and Teams: how people ask Qubit once it is on.
• Q-Director: Slack, Teams and agent mapping: the credentials and the agent mapping behind automatic linking.
• Linking your Slack or Teams account: how people link their own account.
• MCP sources: the sources this page lets you limit.
• Routines: what the routines list shows and how people create them.