The QuantumOps launcher tab in HaloPSA

The QuantumOps launcher is a small page that you add to HaloPSA as a custom tab. It shows which ticket or client the tab belongs to and gives technicians a way in: open the QuantumOps side panel, open the dispatch board, install the extension, or open the record in the QuantumOps web app. The tab holds no session and reads nothing from HaloPSA. The side panel signs in separately. A HaloPSA administrator sets the tab up once, and technicians then use it without further setup.

Before you start:

• The launcher must be switched on for your instance. The Switched on for this server card on the Browser Extension page shows a Halo launcher tab badge when it is. When it is off, the launcher card is not listed in Dashboard Setup and the tab does not open.
• You need the Administrator or Q-Director Configuration role to copy the URL from Q-Director Config → Dashboards (the setup wizard step needs the Administrator role), and a HaloPSA administrator account to create the custom tab.

What technicians see

With the extension installed in their browser, the tab shows what it detected as chips: Ticket with the ticket number, or Client with the client number on a client tab, and Agent with the signed-in technician's own HaloPSA agent number. It shows No entity in this tab when the address carries no record number. It says The QuantumOps panel is installed in this browser. and offers two buttons:

• Open the QuantumOps panel opens the side panel next to HaloPSA.
• Open the dispatch board opens the board in its own browser tab.

Without the extension, the tab shows Install the QuantumOps extension with links for Chrome, Microsoft Edge and Firefox. A link goes to the store listing when your instance has one for that browser. Otherwise it goes to the Browser Extension page in the web app, with a note to sign in to the web app first. The tab also has an Open in the QuantumOps web app button. For a ticket or a client it opens that record's dashboard page; for other tabs it opens the web app.

For a moment after the tab loads, before the extension answers, the install card can show even when the extension is installed.

Add the launcher tab to HaloPSA

1. In QuantumOps, open the QuantumOps Panel (launcher) card. It is on the Dashboard Setup step of the setup wizard, and on Q-Director Config under Dashboards. Copy its URL: select Copy next to Dashboard URL in the setup wizard, or the copy icon (Copy URL) on Q-Director Config → Dashboards. Adding QuantumOps tabs to HaloPSA describes where the cards are.
2. In HaloPSA, go to Configuration → Custom Objects → Custom Tabs, select Ticket and then New. Set the type to iFrame, paste the URL and clear Show menu.
3. Tick Send secure URL parameter and copy the tab's Iframe secret from HaloPSA. HaloPSA uses the secret to sign the agent placeholder in the URL. Ask TechPulse to set that secret for your instance, because QuantumOps checks each tab's signature against it.
4. Enable the tab on each ticket type under Configuration → Tickets → Ticket Types → Custom Tabs. The card recommends putting it first.
5. Open a ticket in HaloPSA and check that the tab shows the ticket number.

The URL has the shape below. Copy it from the card rather than typing it, and leave every placeholder as it is. HaloPSA fills them in when the tab opens, and the agent placeholder is the part HaloPSA signs, so it has to stay.

https://yourcompany.qops.app/halo/launcher?tenantId=<your organisation id>&ticketId=$FAULTID&agentId=$LOGGEDINAGENTID&hmac=$HMAC

The card is for the Ticket entity. For a custom tab on the Client entity, replace ticketId=$FAULTID with clientId= followed by the client placeholder that the Client Dashboard card's URL uses, and keep agentId=$LOGGEDINAGENTID and hmac=$HMAC unchanged.

What happens without the signature

The tab refuses to open until it can prove it comes from your HaloPSA:

• With a secret set on your instance, the URL's signature must verify. A tab whose signature does not match says This tab could not be verified. The secret in HaloPSA is then not the one your instance has.
• Until a secret is set, the tab accepts your tenant tab key instead. Add &tk= and the key to the URL. Adding QuantumOps tabs to HaloPSA shows how to create the key.
• With neither, the tab says This tab is not configured.

The page can be shown only inside your own HaloPSA, and in any extra sites you list for framing in Dashboard Setup.

Custom HaloPSA domains

The launcher works on a custom HaloPSA domain, but the panel that it opens still needs the browser's permission for that domain, once per technician. See Setting up the extension.

Replace the embedded dashboards with the launcher

The dashboards that run inside HaloPSA tabs can be switched to show the launcher card in place of their normal content. This is available when enabled for your organisation; ask TechPulse to turn it on. Until then the dashboards keep working as before, even when the launcher card is listed.

When it is on:

• The Ticket Dashboard, Ticket Triage Dashboard, Agent Assist (Interactive Guide) and Client Dashboard tabs, and the Qubit chat tabs for tickets and clients, show the launcher card. The User Dashboard and Agent Dashboard pages show it too, but HaloPSA has no tab for either of them yet; see Adding QuantumOps tabs to HaloPSA.
• The URLs of your existing HaloPSA tabs do not change.
• It applies to your whole instance. A technician without the extension sees the install links and a link to the web app, not the dashboard. The card's link to the web app opens the same dashboard address, which shows the launcher card too, so it does not give back the dashboard.
• For a browser with no store listing, the card does not link to the Browser Extension page. It asks the technician to get the install link from their administrator.
• Turning it off brings the dashboards back the next time a tab loads.

Each embedded tab has an equivalent in the panel:

Plan the move from the dashboards to the extension

1. Roll the extension out to everyone who uses the dashboard tabs; see Rolling out the extension to technicians.
2. Add the launcher tab and put it first on your ticket types. Keep the existing dashboard tabs while technicians move over.
3. Let technicians work from the panel for a while and compare it with the dashboards they used, using the table above.
4. List anyone who cannot install the extension, for example where a browser policy blocks extensions. While the replacement is on, they have no QuantumOps dashboard inside HaloPSA, because the card's link to the web app opens a page that shows the same card. The replacement applies to your whole instance, so decide whether they can work without the dashboards before you ask for it to be switched on.
5. Ask TechPulse to switch the replacement on when everyone is ready. You can leave the old tabs in place; each then shows the launcher card.

Next steps

• Adding QuantumOps tabs to HaloPSA: the dashboards and the tab key.
• Rolling out the extension to technicians: install the extension on managed devices.
• The QuantumOps browser extension: where technicians get the extension.
• Opening the dispatch board: what the board button opens.