HaloPSA integration

1. Create an API application in HaloPSA

1. In HaloPSA, go to Configuration › Integrations › HaloPSA API.
2. Add a new application using the Client ID and Secret (Services) authentication method.
3. Give it permission to read clients, ticket types, statuses, and priorities, and to create and update tickets and add actions. We request the all scope.
4. Copy the client ID and client secret.

2. Connect in Client Posture

1. Sign in as an owner or admin and go to Settings › Integrations.
2. Enter your HaloPSA instance URL (HTTPS, for example https://yourcompany.halopsa.com), client ID, and client secret.
3. We test the credentials before saving. The client ID and secret are encrypted at rest.

3. Settings and client mapping

• Ticket type: required before any ticket is created.
• Closed status: required before any ticket is closed.
• Priority by severity: optional. Leave a severity on Halo default to let HaloPSA choose.
• Map each Client Posture client to a HaloPSA client. Unmapped clients never create tickets.

How tickets work

• After each scan of a mapped client, we open one ticket per verified fail or warning. Each check gets one ticket per client: if a check was ticketed before, even if that ticket was closed, we do not open another. The ticket summary is “Client Posture: check title” and the body explains the finding and the recommended fix.
• A ticket is closed only when the previous scan verified the problem and the new scan verifies a pass. We add a hidden note, then set your closed status.
• Unknown and Not tested results never open or close tickets.

Disconnect

An owner or admin can click Disconnect in Settings › Integrations. We delete the stored credentials. Tickets already in HaloPSA stay there. Each sync is recorded in the integration log on the same page.

Support

Questions or problems: contact us.