NetLock RMMNetLock RMM Docs
IV — Administration

HaloPSA

Connect NetLock RMM to HaloPSA: alerts become tickets of the mapped client, the all-clear adds a hidden note and sets the closing status, devices can be synced as assets, clients and sites can be imported.

HaloPSA

Requirements

  • An API application in HaloPSA under Config > Integrations > Halo API, with the authentication method Client ID and Secret, the permission scope all, and an agent it runs as.
  • For a hosted instance, its tenant name, which is shown on the same page.

Setup

  1. In Settings → Integrations, open the HaloPSA tile and choose Connect.
  2. Enter the Instance address, for example https://company.halopsa.com, the Client ID and the Client secret, and for a hosted instance the Tenant. An Authorisation server is only needed if it is not located at /auth on the instance.
  3. Under options, choose the Ticket type and the Closing status, and optionally a Team. Outcome of the note is the action outcome that writes a private note.
  4. Map each tenant to a client, or import clients and sites. Tenants without a mapping are not included.
  5. Optionally map locations to sites and severities to priorities.
  6. Activate the connection.

The API allows 700 requests in five minutes per tenant; a job that hits this limit waits and then continues.

What goes to the vendor

For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.

With the asset sync on, also: device name, operating system, manufacturer, model, serial number, IP address and MAC address.

What happens to a ticket

  • An alert becomes a ticket of the mapped client, at the mapped site if there is one. The reference NetLock-Alert-<id> is added at the end of the summary.
  • When the alert ends, the ticket gets a note hidden from the user, without an e-mail, and it is set to the closing status if nobody is working on it.
  • A ticket with an agent counts as assigned.
  • If Halo refuses the status, for example because of a field required on closing, the ticket stays open with its note, and the history says close_refused.

The behaviour is set in the Settings tab, see A.14.4. NetLock never deletes anything at the vendor.

Asset sync

The sync is off by default. Assets can count towards a license in Halo. Switch on Sync devices as assets, and map device classes to asset types or choose a Default asset type. A device of a class without a type is named in the history and waits; the other devices are still processed.

  • An asset carries NetLock-Device-<id> as inventory number. NetLock reuses an existing asset only on an exact match.
  • A device without a location mapping goes to the main site of its client.
  • The fields of an asset type differ per instance, so the device details are written to the notes of the asset.
  • A device that moved to another client gets a new asset there. The old one stays.
  • An alert of a synced device links the asset to the ticket.

Contract quantities

The HaloPSA connector does not write contract quantities. The asset sync keeps the assets of each client current, which a recurring item in HaloPSA can count.

Known limits

  • Tickets in NetLock show the ticket id, no link.