Setting up the extension

After you install the extension, you connect it to your QuantumOps instance, sign in and open a HaloPSA ticket. This page walks through those steps and the settings you may need later: allowing a custom HaloPSA domain and choosing where the panel shows.

Before you start: install the extension first; The QuantumOps browser extension explains how. You also need your instance address, which the Browser Extension page shows with a Copy button, and your QuantumOps login. On a managed device your administrator may have installed and pre-configured the extension; the address may already be set, and you can go straight to signing in.

Connect the extension to your instance

1. The first time the extension runs, it opens a welcome page in a new tab. It says QuantumOps for Halo is installed and lists three steps: connect, sign in, open a HaloPSA ticket. Select Open options. You can open Options later from the gear in the panel's status bar, or from the browser: right-click the toolbar icon and choose the extension's options entry (Options in Chrome, Extension options in Edge). In Firefox, open the add-ons page (about:addons), select QuantumOps for Halo and open its options.
2. Under QuantumOps instance, enter your instance address, for example https://yourcompany.qops.app, and select Use this URL.
3. If your address is not on one of the standard QuantumOps domains (a privately hosted instance, for example), the browser asks for permission to let the extension reach it. Allow it, or the panel cannot call your instance.
4. A message confirms Configuration loaded from your address. The extension has downloaded the sign-in settings from your instance. Leave Sign-in settings (advanced) alone unless your administrator tells you to change something there.

If the address is not valid, Options says Enter a valid https URL for your QuantumOps instance. If you decline the browser's permission, it says Permission for the API origin was not granted; the panel cannot call it. Select Use this URL again and allow the permission. If the address is valid but the extension cannot load the sign-in settings from it, Options says Could not load configuration from followed by your address and a reason. Check that the address is the one the Browser Extension page shows for your instance.

An address set by your administrator's browser policy wins over what you type here.

Sign in

1. Select the QuantumOps icon in the toolbar to open the panel. Pin the icon first if you cannot see it.
2. Select Sign in to QuantumOps. A browser window opens on your organisation's sign-in page. Sign in the way you do for the QuantumOps web app. The button reads Waiting for sign-in… until the window closes, and then your name appears in the status bar at the bottom of the panel.
3. If the panel shows Set the QuantumOps URL instead of the sign-in button, the extension does not have your instance's sign-in settings yet. Open Options and select Use this URL again.

The extension never sees your password. Your session stays in the browser's memory and ends when the browser closes. When the browser starts, and after an extension update, the panel first tries to sign you in without asking; if your organisation's sign-in session is still open, you are signed in again, and otherwise the sign-in button appears.

After you select Sign out, the panel does not sign you in again by itself; it waits until you select Sign in to QuantumOps in the panel or Sign in in Options. Signing out also opens a tab on your organisation's sign-in service to end that session.

What your account needs

• A QuantumOps organisation. The account must belong to your organisation's QuantumOps. Otherwise the panel reports No tenant: the signed-in account is not linked to a QuantumOps organisation. Use the account you use for the web app, or ask your administrator.
• A link to your HaloPSA agent, to write to HaloPSA. QuantumOps links your login to your HaloPSA agent by matching the e-mail address you signed in with, which the sign-in service must have verified, to the agent's e-mail address in HaloPSA. An administrator can also link them by hand with Link a HaloPSA agent in Team Management. Until the link exists the panel is read-only: the buttons that would write are greyed out, and a Read-only chip explains why. Nothing needs reinstalling once the link is made.

How the panel follows HaloPSA

When you open a HaloPSA page, the extension reads the ticket, client, user or agent number from the page address and the panel switches to that record. It never reads or changes the page itself, and it keeps up when HaloPSA moves to another record without reloading.

• On a ticket, the panel header shows the ticket number and the Ticket, Triage and Assist tabs fill in.
• On a client, user or agent page, the panel switches to that tab.
• On any other page, the header says Not on a Halo page.

This works without any setup on HaloPSA's standard domains: any address under halopsa.com, haloitsm.com or haloservicedesk.com. A custom domain needs one more step.

Allow a custom HaloPSA domain

If your HaloPSA runs on a domain of your own, for example servicedesk.yourcompany.com, the browser has to give the extension access to that domain once. There are two ways.

From the prompt in the panel. After you sign in, your instance tells the panel which HaloPSA it is connected to. When that is a custom domain the browser has not allowed yet, the panel shows Allow QuantumOps on followed by the domain. The prompt explains that the browser asks once before the panel can follow the domain's tickets, and that nothing else on the domain is read.

1. Select Allow on followed by the domain.
2. Accept the browser's permission prompt.
3. Reload your HaloPSA tab.

Not now puts the prompt off. The choice is remembered for that domain, so the panel does not ask every time it opens; you can still allow the domain later from Options. If you refuse the browser's prompt, the panel says The browser did not grant it. and the button stays available.

From Options. Open Options and go to Halo URLs.

1. Type the domain in the box under Halo URLs, for example servicedesk.yourcompany.com.
2. Select Add Halo URL and accept the browser's permission prompt. If the browser does not grant it, Options says Permission was not granted.
3. Reload your HaloPSA tab.

The list under the box shows every domain you have allowed:

Above the box, your instance's own HaloPSA shows Works without a permission prompt and the From your QuantumOps instance mark when it is on a standard domain.

If your administrator blocks HaloPSA for extensions with a browser policy, the panel cannot follow it. Troubleshooting the extension shows how to check.

Choose where the panel shows

In Chrome and Edge, Options has a Side panel section with the box Show the panel only on Halo tabs (Chrome and Edge). When it is ticked, the panel hides on other sites and comes back when you return to HaloPSA. The toolbar icon still opens it on any tab, and QuantumOps pages keep it available.

The box is ticked by default in Chrome and not ticked in Edge, because Edge may not bring the panel back when you return to a tab. Firefox ignores the setting, because its sidebar cannot be hidden for a single tab. When your administrator has set the choice by policy, the box is read-only and shows Managed by policy.

Check who is signed in

The Account section of Options shows Status (Signed in as followed by your name, or Signed out), Token expires, the time the current sign-in token runs out (the extension renews it in the background), and Last error. Use Sign in or Sign out there as well. Sign in stays unavailable until the instance address is set and its sign-in settings have loaded.

Next steps

• Finding your way around the side panel: the tabs, the More menu and the status bar.
• Troubleshooting the extension: what to do when sign-in or page following does not work.
• What each part of the extension needs: which roles and switches each tab depends on.
• Rolling out the extension to technicians: for administrators installing it on many machines.