HaloPSA

Map Level groups to HaloPSA sites, sync the assets, and choose which monitor policies create tickets.

Overview

Devices in mapped groups sync as HaloPSA assets. Selected monitor policies open tickets of the mapped ticket types. Groups map to HaloPSA companies and sites.

How it works

  • Put devices in the right site.

    Map any Level group or subgroup to a HaloPSA company and site.

  • Sync assets automatically.

    Devices in mapped groups become HaloPSA assets when the connection is enabled.

  • Choose what opens a ticket.

    Map selected monitor policies to the HaloPSA ticket types your team uses.

Set up the integration

  • Create a HaloPSA application.

    Use a scoped API application and agent with the required asset and ticket access.

  • Connect the application in Level.

    Add the HaloPSA URL, client ID, and client secret, then test the connection.

  • Map, enable, and watch the events.

    Map groups and monitor policies, enable sync, and verify requests in Events.

Questions about this connection.

What does the HaloPSA integration sync?

Devices in mapped groups sync as HaloPSA assets. Selected monitor policies open tickets of the mapped ticket types. Groups map to HaloPSA companies and sites.

Does Level replace HaloPSA?

No. Level is the RMM. HaloPSA stays the system of record for its own job.

Where is the setup guide?

The setup steps live in the HaloPSA integration guide.

Is there a free trial?

The first 10 devices are free forever. No time limit.

Which monitor policies create tickets?

You choose. Map selected monitor policies to the HaloPSA ticket types your team uses. Groups map to HaloPSA companies and sites. Devices in mapped groups become assets.

Put HaloPSA and Level in the same workflow.

Start free, follow the setup guide, and keep device work moving into the system your team already uses.