Einführung
This integration syncs Level devices into HaloPSA as assets and routes Level alerts to HaloPSA tickets. Setup happens in three stages: configure a HaloPSA application, connect it in Level, then map your device groups to HaloPSA sites and choose which monitor policies create tickets.
⚙️ PREREQUISITES
Level administrator access
HaloPSA administrator access with permission to create applications and manage agents
HaloPSA Integration
Konfigurieren HaloPSA Application
HaloPSA uses "Anwendungen" to allow API access. We need to create one for Level.
1. Go to Einstellungen > Integrationen:
2. Klicken Sie auf "HaloPSA API":
3. Take note of the base URL shown below. This will be used as the "HaloPSA URL" when configuring Level:
4. Klicken Sie auf "Ansicht Anwendungen":
5. This is a list of your existing "Anwendungen". Klicken Sie auf "New" in the top-right corner to create an application for Level:
6. Complete the required "Application Name" field with a name of your choice. Wählen Sie the "Client ID and Secret (Services)" option:
7. Make note of the "Client ID" and "Client Secret" as we will need those when configuring Level.
8. Wählen "Agent" for the "Login Geben Sie" and select the agent you wish for Level to use.
💡 TIPP: HaloPSA recommends creating an "API only" agent for integrations. This type of agent doesn't count against your license seats.
9. Klicken Sie auf "Speichern":
10. Klicken Sie auf "Berechtigungs":
11. Wählen Sie the following permissions:
read:tickets
edit:tickets
read:customers
read:assets
edit:assets
ℹ️ NOTE: Halo recently made a change that prevents non-admin integrations from adding fields to asset types. They are working on reverting the change, but it will take approximately two weeks (around Neinvember 19th). In the meantime, if you're setting your Halo integration up for the first time, please grant "admin" permission to the application and the agent. Sorry for the trouble.
12. Klicken Sie auf "Speichern" when finished:
Konfigurieren HaloPSA agent permissions
The API agent that you set in the previous step for the "Agent to log in as" requires a couple of permissions to work properly.
1. Go to Einstellungen > Teams & Agents > Agents and choose the agent assigned to the application:
2. Klicken Sie auf on the "Berechtigungs" tab and enter "Bearbeiten" mode:
3. Make sure the following settings are set:
Tickets Access Level - Read and Modify
Clients Access Level - Read Only
Assets Access Level - Read and Modify
Can add new Tickets - Ja
Allow use of all Ticket Geben Sies - Ja
4. Klicken Sie auf "Speichern" when finished:
Konfigurieren integration in Level
1. Go to Einstellungen > Integrationen:
2. Klicken Sie auf on HaloPSA integration:
3. Complete the three configuration fields:
HaloPSA URL
The URL you use to access your HaloPSA instance. This URL can point to an on-premises or cloud location and should include the appropriate protocol. For example: https://domainhalopsa.com.
Client ID
The value we generated in the previous steps.
Client secret
The value we generated in the previous steps.
4. Klicken Sie auf die "Speichern changes" button:
5. Press "Test connection" to make sure your settings are working:
Map Level groups to HaloPSA sites
Level will create assets in HaloPSA based on your group mappings. You can choose any group or subgroup in Level and match it with a company and site combo from HaloPSA.
1. Go to "Gruppe mapping":
2. Klicken Sie auf "Hinzufügen new groups" to select the Level groups to map to HaloPSA sites:
3. Wählen one or more groups and click "Hinzufügen new groups":
4. Wählen a HaloPSA company for the first mapping:
5. Wählen Sie the HaloPSA site:
6. Repeat for every row and click "Speichern" when finished:
ℹ️ HINWEIS: The integration remains disabled at this stage, so no devices are synced yet.
Map Level monitor policies to HaloPSA ticket types
Level can map alerts to HaloPSA tickets. We just need to select which monitor policies should create tickets, as well as which ticket types they should be created as.
1. Klicken Sie auf on "Ticketing":
2. Wählen HaloPSA ticket types for each policy that you wish to map:
3. When finished, click "Speichern changes" at the bottom of the page:
ℹ️ HINWEIS: The integration remains disabled at this stage, so no devices are synced yet.
Start sending devices and alerts
1. Klicken Sie auf die "Deaktivierend" toggle:
2. This will immediately begin sending devices and alerts. You can see the group mappings change from "Unsynced" to "Syncing" and eventually to "Synced":
3. If you want to follow the progress, or troubleshoot an issue, navigate to the "Events" tab to see a real-time list of requests being sent to HaloPSA:
Häufig gestellte Fragen
Who can configure this integration? A Level administrator. The HaloPSA side also requires an administrator with permission to create applications and manage agents.
Do I need to create a dedicated HaloPSA agent for this? HaloPSA recommends it. An "API only" agent doesn't consume a license seat and keeps integration activity separate from human agent activity.
Will all devices sync immediately when I enable the integration? Ja. Enabling the toggle starts syncing all devices in mapped groups. Watch the group mapping table — rows move from Unsynced to Synced as devices are processed.
Why isn't a device showing up in HaloPSA? Check that the device's group is mapped under Gruppe mapping and that the integration is enabled. Then open the Events tab and look for failed requests related to that device.
Can I map more groups after the integration is live? Ja. Go back to Gruppe mapping, add new groups, and save. New groups sync after the mapping is saved.