Overview
Connecting HaloPSA to Overe lets you raise Halo tickets from Overe Alerts automatically. Each ticket is created against the right customer, so you don't have to triage alerts or re-enter details by hand.
The setup has three parts:
Create an API application in HaloPSA.
Connect HaloPSA in Overe.
Map your Halo customers to Overe Sites.
Important: Connecting HaloPSA does not onboard any customers into Overe by itself. Halo decides who your customers are, and you decide which of them are onboarded into Overe and linked.
Before you start
You need administrator access to your HaloPSA instance so you can create an API application.
You need access to Config & Billing for your organisation in Overe.
Have your Halo instance URL ready, e.g.
https://yourcompany.halopsa.com.
Step 1: Create an API application in HaloPSA
In HaloPSA, go to Configuration > Integrations > HaloPSA API and select View Applications.
Select New and give the application a recognisable name, e.g. Overe.
Set the Authentication Method to Client ID and Secret (Services).
Set the Login Type to Agent and choose the agent that tickets and assets should be created as. A dedicated integration agent makes Overe activity easy to spot in Halo.
On the Permissions tab, grant access to read customers and sites, create and update assets, and create tickets.
Save the application, then copy the Client ID and Client Secret. Store the secret somewhere safe, because Halo may not show it again.
For more detail on API applications, see Halo's guide: How to create a Halo API application.
Step 2: Connect HaloPSA in Overe
In Overe, go to Config & Billing and open the PSA Connectors tab.
On the HaloPSA tile, select Connect.
Enter the following details:
Halo instance URL: the base URL of your Halo web application, e.g.
https://yourcompany.halopsa.com.Client ID: from Step 1.
Client secret: from Step 1. You can use the eye icon to check what you've entered.
Review the permissions Overe will use: Read customers and sites, Create and update assets and Create tickets.
Select Continue to mapping.
When the connection succeeds, the HaloPSA tile shows Connected, your Halo instance and when it last synced. It also shows a count of unmapped customers, which are the Halo customers you haven't linked to an Overe Site yet.
Your client secret is encrypted at rest and is never included in logs, events or support diagnostics.
Step 3: Map Halo customers to Overe Sites
Mapping links each Halo customer to the Overe Site that represents it. Overe can only raise tickets for a customer once it's mapped.
To open the mapping screen, select the HaloPSA tile on the PSA Connectors tab. It has two tabs:
Current mappings shows the Halo customers discovered most recently, followed by a table of every existing Site-to-customer mapping.
Unmapped customers lists every Halo customer Overe has found that isn't mapped yet. You can search the list, and new customers appear here automatically as they're added in Halo.
Each unmapped customer has two options.
Option A: Map to an existing Site
Use this if the customer is already onboarded in Overe.
Select Map to a Site next to the Halo customer.
Search for the Overe Site and select it.
Some Sites appear greyed out because they can't be selected:
Mapped to [customer name] means the Site is already linked to another Halo customer. Each Site can be mapped to only one Halo customer, and each Halo customer to only one Site. To change it, remove the existing mapping first.
Not synchronized yet, try again after the next sync means the Site hasn't completed its first sync with Overe yet. Try again after the next sync.
Option B: Create a new Site
Use this if the customer isn't in Overe yet.
Select Create a Site next to the Halo customer.
Overe creates a new Site for the customer and maps it straight away.
Finish onboarding the new Site in the usual way, including connecting the customer's Microsoft 365 tenant.
You don't have to map every Halo customer. Leave a customer unmapped if you don't protect it with Overe.
After setup
Tickets
Once a customer is mapped, Overe creates a ticket in HaloPSA against that customer whenever an Alert is raised for its Site. No other Overe activity creates tickets.
Syncing
Overe syncs with HaloPSA once a day, and picks up new Halo customers during each sync. To sync straight away, for example after adding a customer in Halo, select Sync now on the HaloPSA tile.
Removing a mapping
On the Current mappings tab, select Remove next to the mapping. This only unlinks the Site from the Halo customer. Nothing is deleted in Overe or in Halo, and the customer goes back to the Unmapped customers list.
Updating connection details
If you rotate the client secret or change your Halo URL, open the ⋮ menu on the HaloPSA tile, select Edit and enter the new details.
Troubleshooting
A new Halo customer isn't showing as unmapped. Select Sync now, or wait for the next daily sync.
I can't select a Site when mapping. Check the reason shown under the Site name. Either it's already mapped, or it hasn't synced yet.
Tickets aren't being created for a customer. Make sure the customer appears on the Current mappings tab, and that the Halo API application still has permission to create tickets.
The connection stopped working. If the client secret has expired or been regenerated in Halo, update it using Edit on the HaloPSA tile.
For background on how the integration works, see PSA Integration in Overe.