What Qubit can use: tools and sources

Qubit answers from what it can look up. This page lists the tools behind Chat with Qubit, explains how to narrow them for the next answer, and shows how to open a document that Qubit cites.

Before you start: Everyone who can use the chat can use the tools their organisation has set up. Look-ups in HaloPSA need your organisation's HaloPSA connection, which your administrator sets up. Documentation needs the Documentation module and a documentation source that has been synced. Support memory is available when enabled for your organisation. MCP sources are available when your organisation or you have connected them.

What Qubit can do from chat

Qubit chooses the tools itself. You see each one it uses as a row in the answer, and you can open the row to read what it asked and what came back.

Whose access Qubit uses

• HaloPSA look-ups use the HaloPSA connection that your administrator set up for the organisation, not your personal HaloPSA login.
• A tool from an MCP source runs with that source's connection. A source set up for each person uses your own connection, so you connect it once. A source shared by the whole organisation uses the shared connection.
• Every tool call is governed by Tool Governance and recorded in an audit. Reading tools run without asking, and tools that change something ask first. See Approving Qubit's actions and Tool Governance.

Choose the tools for the next answer

Use the tools button when you want Qubit to stay away from some tools, for example to keep an answer to your documentation only.

1. Select the tools button in the bar under the chat header. It reads All sources until you narrow it, then No tools or a count such as 3 of 5 sources. Hover over it to see the tools that are on.
2. In Tools the assistant may use, switch each source on or off:
   • Halo covers tickets, clients, users and agents.
   • Support memory covers facts about clients, users, sites and assets, and past resolutions.
   • Documentation covers IT Glue, Hudu and SharePoint articles, cited as footnotes.
   • Below them, each MCP source is listed by name.
3. For a source that is marked needs your sign-in, select Connect. It opens the MCP Sources page, where you connect it; see MCP sources. Then come back and switch it on.
4. Select Done.

To go back to the full set, select Everything. The link appears whenever you have narrowed the tools.

Keep in mind:

• The choice only narrows. It can never give Qubit a tool that your organisation or your own connections do not already allow.
• QuantumOps remembers your choice in this browser and saves it with each conversation, so an action you approve later runs with the same tools.
• The tools button is off while an answer is running and on a read-only Slack or Teams conversation. While the list loads it reads Sources…, and if it cannot load, the menu says Could not load the source list.
• When no MCP source is set up for you, the menu says No MCP sources are configured for you yet.

Why a source is greyed out

A greyed-out source has a line under its name that gives the reason.

• Support memory is greyed out when support memory is not enabled for your organisation.
• Documentation is greyed out when documentation is not available to chat. The usual reasons are that the Documentation module is off, the master switch Documentation search in AI is off, the Use in Qubit chat switch is off, no source type is enabled for search, or nothing has been synced and indexed yet. Administrators change these in the Documentation Hub Settings tab or on the Q-Director Research & Docs tab. The settings table matches the labels on the two screens.
• An MCP source marked needs your sign-in is not greyed out. It works once you connect it.

Numbered sources under an answer

When Qubit answers from your documentation, the text carries numbered markers such as [1] and [2], and the sources are listed under the answer, each as its number, its title, and the source type and client after it (for example IT Glue · Contoso). Select a marker or a title to open the source:

• A document that has a web link of its own opens that link in a new tab.
• A document with no web link of its own opens in the Documentation Viewer, described below.

Hover over a title to see an excerpt of the passage Qubit used. A number never changes once you have seen it, even when an approval lets the answer continue.

Open a document in the Documentation Viewer

The Documentation Viewer shows one synced documentation item, and lets you browse the rest. Any signed-in user can open it, either from a cited source or at /documentation/viewer.

1. Select a cited source with no web link of its own. The viewer opens on that document.
2. Read the document on the Content tab. Metadata shows the external ID, the organisation and the dates, and whether the item is processed (Is Processed) and indexed for AI search (Has Vector). Raw Data shows the item as it was received from the documentation source.
3. Select Close to go back to the list, or Back to return to the Documentation Hub.

To browse instead, open the viewer without a document. Documentation Items lists every synced item with its source, modification date and status. To narrow the list:

• Type in Search to match titles and text.
• Pick a Source, an Item Type or a Date Range.
• Select Clear All Filters to start again.

Quick Stats shows how many items there are, how many match your filters and how many are Vectorized, which means indexed for AI search. Select View on a row to open it, and Refresh to reload the list.

Related pages

• Chat with Qubit: the chat itself.
• Approving Qubit's actions: when Qubit asks first.
• MCP sources: how to connect more tools.
• HaloPSA's native MCP source: HaloPSA's own tools for Qubit.
• Documentation Hub: where administrators manage the documentation that Qubit searches.
• Tool Governance: where administrators decide which tools run, ask or are blocked.