The QuantumOps browser extension

QuantumOps for Halo is a browser extension for Chrome, Microsoft Edge and Firefox. It shows your QuantumOps instance in a side panel next to HaloPSA and follows the page you have open: a ticket, a client, a user or an agent. Dispatchers can also open the dispatch board in a browser tab of its own. Everything the panel shows comes from your own QuantumOps instance, and the extension reads only the record number from HaloPSA addresses. Chrome and Edge show the panel as a side panel; Firefox shows it in the sidebar.

Before you start: you need a QuantumOps login. Every signed-in user can open the Browser Extension page and install the extension. What the panel shows after that depends on your role and on what is switched on for your instance; see What each part of the extension needs. To write to HaloPSA from the panel, your login must also be linked to your HaloPSA agent.

Open the Browser Extension page

Select Browser Extension in the left menu (the page is at /extension). The page is titled QuantumOps for Halo and has three parts: download cards for each browser, details for connecting the extension to your instance, and a built-in guide.

Badges along the top show:

• the extension version your instance ships as a downloadable bundle;
• the version each store is serving right now, when your instance can read it;
• the version of the QuantumOps server;
• Sideload build, the kind of package the download cards hand out.

When the extension is already installed in the browser you are using, the page compares its version with the store and the bundle. If it is behind, a note says which version you have and how to update. If it is current, a badge says so.

Install from a store

The Chrome and Firefox cards link to the extension's store listing (install from the store). Edge installs the extension from the Chrome Web Store, so the Microsoft Edge card shows a store link only when your instance has an Edge Add-ons listing of its own.

A store install updates itself. Your browser installs each new version a few hours after the store approves it, and you download nothing from this page.

Download and load a bundle

The cards for Chrome, Microsoft Edge and Firefox also offer the extension as a downloadable test bundle. Each card lists:

Select Download to save the bundle. If your server was built without bundles, the cards say so; ask your administrator for the bundle. Treat a bundle as a test build: do not upload it to a store or share it outside your team.

To load a bundle in Chrome or Edge:

1. Unzip the bundle into a permanent folder. The browser loads the extension from that folder every time it starts, so do not leave it in your downloads folder.
2. Open chrome://extensions in Chrome or edge://extensions in Edge and turn on Developer mode. Edge then shows a banner about sideloaded extensions; that is expected.
3. Select Load unpacked and choose the folder.
4. Pin the extension to the toolbar so that its icon is always visible.

Release and Beta Firefox run the unsigned bundle only as a temporary add-on. Firefox Developer Edition, Nightly and ESR can also install it persistently; the Install chapter of the built-in guide on this page has those steps. To load it as a temporary add-on:

1. Save the .xpi file where you can find it again.
2. Open about:debugging#/runtime/this-firefox. Do not use about:addons: Release Firefox answers that with This add-on could not be installed because it appears to be corrupt. The file is not damaged.
3. Select Load Temporary Add-on… and choose the file.

Firefox removes a temporary add-on when it closes, so load it again after each restart.

Connect the extension to your instance

The Connect it to this instance card shows your instance's address in a read-only QuantumOps instance box, with a Copy button. After you install the extension, paste this address into the extension's Options. Setting up the extension walks through it.

Under the box, two badges can appear:

• Sign-in configured on this server means sign-in is ready. When it is not, the page warns that the panel opens but sign-in cannot start; tell your administrator.
• Server supports the whole guide means the server is new enough for every chapter of the built-in guide. When it is not, the page warns that some sections of the guide will be missing.

The Switched on for this server card lists eight features, each with a check mark when it is on for your instance and a dash when it is off: Ticket · Triage · Assist, Chat (Qubit), Dispatch board, Call tab, Clock tab, Call recordings, Caller verification and Halo launcher tab. Your licences, your role and your HaloPSA agent link decide the rest.

Read the built-in guide

Below the cards, the page has a guide with one tab for each chapter: Install, First run, Using the panel, Client · User · Agent · Call · Clock, Dispatch board, Troubleshooting and Reference. People with the Administrator role also get an Administrators chapter, with the sign-in, switch and rollout settings of your instance; everyone else does not see that tab. The guide reads the facts of your instance, such as its address and whether sign-in is configured. This documentation covers the same ground in more detail: Setting up the extension, Finding your way around the side panel, Troubleshooting the extension and Rolling out the extension to technicians.

Keep the extension up to date

How an update arrives depends on how you installed the extension:

• Installed from a store, or by your administrator's policy. The browser fetches the new version itself. The extension tells you about a version only after its store serves it.
• Loaded from a bundle. You replace the files. Download the new bundle from the Browser Extension page, replace the contents of the folder you loaded the extension from, then select Reload on the extension's card in the browser's extensions page. In Firefox, load the new .xpi again. Your instance address and custom HaloPSA domains are kept; you sign in again.

The extension checks for a newer version every six hours, when the browser starts, after the extension is installed or updated, and when you save a new instance address. It shows the result in four places:

• A banner under the panel's tab strip. On the sign-in screen, which has no tab strip, it sits at the top, because the check does not need a login. The banner reads Update needed for an ordinary update, Update required when your version is below the minimum your instance still supports, and is ready to install when the browser has already downloaded the update. Its buttons depend on the install. Update now asks the browser to look for the update, and opens the store page when the browser does not have it yet (Firefox opens the add-on page). Get followed by the version opens the download page for a bundle install, and Reload extension applies the new files. Restart now finishes an update the browser has downloaded.
• The version in the status bar. When you are behind, the version number gets an arrow (for example v1.2.3 ↑) and turns into a button that starts the update.
• The Updates section of Options. It lists Installed, Served by the store (or Newest on this instance for a bundle install), Minimum supported, Status, Updated by and Last checked, and has a Check for updates button.
• A badge on the toolbar icon. An amber ↑ means an update is available and a red ! means one is required. Hover over the icon to see which version to install. The badge stays until you update.

Later on the banner hides an ordinary update notice for one day for that version. A required notice has no Later button, with one exception: a store install whose browser has not received the update yet can put the notice off for an hour.

Next steps

• Setting up the extension: connect to your instance, sign in and let the panel follow HaloPSA.
• Finding your way around the side panel: the tabs, the More menu and the status bar.
• Each panel tab has its own page: Ticket, Triage, Assist, Chat, Client, User and Agent, Call, Clock and Approvals.
• The QuantumOps launcher tab in HaloPSA: add the launcher to HaloPSA as a custom tab.
• Rolling out the extension to technicians: install it on managed devices.
• Troubleshooting the extension: fixes for common problems.
• Opening the dispatch board: the board that opens in its own tab.