Skip to main content
Manage and troubleshoot

Manage the HaloPSA connection

Check the connection, re-enter the client secret, change ticket defaults, or disconnect HaloPSA, and see what Lemhi can access.

Written By The Lemhi Product Team

Last updated About 24 hours ago

For Lemhi Admins who already connected HaloPSA. Everything below happens on the HaloPSA page: Settings > Integrations > HaloPSA > Manage.

Managing the connection

To do this

Do this on the HaloPSA page

Confirm the connection still works

Select Check connection. A message says "Connection checked. Connected as" with the agent name, or "Connection check failed" with the reason

Replace the client secret, or move to a new API application

Generate a new secret in HaloPSA (Step 3), then select Re-enter secret. Enter the client ID and the new secret, select Test connection, then Save. The web address and tenant name are filled in for you

Change the ticket type, team, or required field values

Under Ticket defaults, pick new values and select Save. Tickets already logged stay as they are

Stop using the integration

Select Disconnect and confirm. Compass can no longer push to HaloPSA. Ticket links on tasks stay as history. Disconnecting also removes your ticket defaults and client mappings, so after reconnecting, set the defaults and run Auto-map again

If you reconnect to a different HaloPSA web address, Lemhi clears the saved ticket defaults, because they belong to the other HaloPSA. Reconnecting to the same address keeps them.

Team members who are not Admins see "Ask a tenant admin to set it up." on the card, or the settings read-only with "Ask a tenant admin to change these settings."

When the connection needs attention

When HaloPSA refuses Lemhi's saved credentials or a permission Lemhi needs, the card shows Connection needs attention with the reason, and the Integrations list shows Needs attention. Pushing tasks is paused until an admin fixes it. Existing ticket links on tasks are unaffected. While the connection needs attention, the ticket defaults are read-only and client mapping is hidden.

  1. Read the reason on the card. It names the HaloPSA setting to fix. Find it in HaloPSA errors and fixes.

  2. Fix it in HaloPSA.

  3. Select Re-enter secret, enter the client ID and secret (a new one if you generated one), select Test connection, then Save.

One PSA per tenant

Lemhi pushes to one PSA per tenant: ConnectWise PSA or HaloPSA, not both. While ConnectWise PSA is connected, the HaloPSA card shows "Disconnect ConnectWise PSA to connect HaloPSA. Lemhi pushes to one PSA per tenant." and Connect is disabled. The ConnectWise card shows the matching line while HaloPSA is connected.

To switch, disconnect the PSA you use now, then connect the other one. Ticket chips from the earlier PSA stay on their tasks as history, still labeled with that PSA's name.

What Lemhi can and cannot access in HaloPSA

Lemhi works only through the API application, API-only agent, and role you created in the setup article, so you control its reach. With the three application permissions and the seven role settings, Lemhi can read your active clients, ticket types, and teams that take tickets; log tickets; read tickets and their status; and add a note to a ticket you link. It never creates clients, never deletes tickets, and never changes a ticket after logging it, apart from the single note on a link.

Lemhi stores your client secret securely and never shows it again after you save. To cut off access at any time, generate a new secret or delete the API application in HaloPSA, or select Disconnect in Lemhi.

Was this helpful?

Still need help? Ask the team