Adding QuantumOps tabs to HaloPSA

The QuantumOps dashboards run inside HaloPSA, as custom tabs on tickets and clients. This page covers adding those tabs, the tenant tab key that unlocks feedback and actions for the people who use them, and the list of sites allowed to show the dashboards in a frame. It is for the Administrator who sets up the HaloPSA side.

Before you start: only an Administrator can open the setup wizard, generate the tab key or change the allowed origins. Q-Director Config, which Administrators and people with the Q-Director Configuration role can open, lists the dashboard URLs only. You also need to sign in to HaloPSA as an administrator to create custom tabs.

Choose which dashboards to add

Each dashboard has a card in the Dashboard Setup step of the setup wizard. The same URLs are listed on Q-Director Config, in the Dashboards tab under HaloPSA Dashboard URLs, which Administrators and people with the Q-Director Configuration role can open (see Q-Director Settings).

The Ticket Dashboard, Agent Assist, Ticket Triage Dashboard and Client Dashboard cards carry the Recommended badge. The Agent Dashboard and User Dashboard cards are marked Coming Soon: the card says HaloPSA does not yet offer what those tabs need, and its Copy button is switched off.

Add a dashboard as a HaloPSA tab

1. In QuantumOps, open the dashboard's card and select Copy next to Dashboard URL. Expand All opens every card. The card also gives Recommended Placement and Tab Order.
2. In HaloPSA, go to Configuration → Custom Objects → Custom Tabs.
3. Select the entity the card names, Ticket or Client.
4. Select New and set the type to iFrame.
5. Paste the URL and save. Leave the placeholders in the URL alone: HaloPSA fills in the ticket or client and the signed-in agent when the tab opens.
6. For a Ticket tab, go to Configuration → Tickets → Ticket Types, edit each ticket type that should show the dashboard, enable the tab under Custom Tabs and arrange the order. A Ticket tab does not appear on tickets until you do this. A Client tab needs no ticket type.
7. Open a ticket or client to check that the tab loads.

Put the tabs in a sensible order

The Recommended Tab Order card on the same step gives two orders:

• Incident and Service Request tickets: Ticket Dashboard first, then Agent Assist, then HaloPSA's own Progress tab.
• Intake and triage ticket types: Ticket Triage Dashboard first, then Agent Assist, then Progress.

You can finish this later. The step says so (You Can Set This Up Later), and the URLs stay available on Q-Director Config.

Set the tenant tab key

The tab key is a secret that you add to your HaloPSA tab URLs as &tk= followed by the key. It proves a dashboard was opened from a tab you set up. What the technician can do depends on it:

Generate the key

1. Open the setup wizard (/setup-wizard) and go to the Dashboard Setup step. The Copilot Identity — Tenant Tab Key card shows Active key configured or No active key.
2. Select Generate Key. When a key already exists the button reads Rotate Key.
3. Copy the key as soon as it appears. It is stored only as a hash and cannot be shown again. If you lose it, rotate to get a new one.
4. Copy the Ready-to-paste Ticket Dashboard tab URL and use it as the URL of the Ticket Dashboard tab in HaloPSA.
5. For the Ticket Triage Dashboard, Agent Assist and Client Dashboard tabs, add the same &tk=your-key to the end of each URL.

Only this step of the wizard manages the key; Q-Director Config lists the URLs and nothing more.

Rotate or revoke the key

• Rotate Key makes a new key and replaces the old one. The old key keeps working for five minutes, so you can update the tabs in HaloPSA without an interruption. After that it stops working.
• Revoke All ends every key at once, with no waiting period. Embedded tabs fall back to view only until you paste a new key. The button appears only while a key is active.

Allow other sites to show the dashboards

Your own HaloPSA address is always allowed to frame the dashboards. If another organisation embeds pages from your instance in its HaloPSA, for example a partner, add that site under Allowed Embedding Origins.

1. In the Dashboard Setup step, find the Allowed Embedding Origins card.
2. Enter each origin, separated by commas, for example https://halo.example.com. Enter https origins only, with no wildcards. Anything after the host name is dropped, so https://halo.example.com/tickets is saved as https://halo.example.com. A wildcard or a non-https entry is rejected with a message that names it.
3. Select Save.

To remove an origin, delete it from the list and select Save again. These origins control framing only. They never give a site access to your data or your API. When White Label Federation is switched on for your organisation, the same list can also be edited on the White Label Federation page under Embedding & CORS origins.

When a dashboard link shows Access Denied

A browser message such as "refused to connect" means the site that frames the dashboard is not allowed: add it under Allowed Embedding Origins. For any other Access Denied page, see A HaloPSA dashboard link that shows Access Denied.

Related pages

• The setup wizard: the step this page works from.
• Copilot suggestions and reply drafts: what the tab key unlocks.
• Access denied and sign-in errors: the page shown when a dashboard link is opened outside HaloPSA.
• The QuantumOps launcher tab in HaloPSA: the launcher that can replace the embedded dashboards.