A step-by-step guide to getting HaloPSA connected
Here are the minimum requirements for on-premise environments.
- Fully Chained SSL Certificate.
- The latest stable version of HaloPSA.
- If your Halo instance restricts access based on IP, our IPs are 3.19.3.152 & 3.19.4.238
Note: On-premise users can populate the Tenant field by typing in the words Not set.
- Upon initial registration of your new account, select HaloPSA and click Next. You will then be presented with a connection checklist. Please gather these items before progressing to the next page. Let's head over to HaloPSA.
- Within Halo PSA, navigate to Configuration > Integrations > HaloPSA API > View Applications.
- Click New in the top right.
- On the Details tab, populate "Application Name".
- Set the "Authentication Method" to Client ID and Secret (Services) and Record the Client ID and Client Secret.
- Set the Login Type to Agent.
- Select an Agent to log in as.
- Ensure the Agent has a Role with the following permissions.
- Admin level
- Read and modify permissions for all feature access options. Tickets, Clients, Users, CRM, Assets, Items, Invoices etc.
- Allow users of all Asset types.
- Configuration options should all be set to Yes.
- Ensure the Agent has a Role with the following permissions.
- Keep a record of the Client ID and Client Secret. Press Save
- On the Permissions tab, enable the following permissions:
- Admin
- Read and Edit to: Customers, Contracts, Items, Invoices, Software, Assets
- Navigate back to the Configurations page. Now go to Teams & Agents > Agents, and ensure Feature Access is enabled for Clients Access Level for the agents you are using.
- Save the API Application.
- Within Halo PSA, navigate to Configuration > Integrations > HaloPSA API and record the Resource Server, Authorization Server and Tenant.
- Return to Gradient, select HaloPSA and insert the following information.
- Client ID
- Client Secret
- Resource Server
- Authorization Server
- Tenant (On-premise users can populate the Tenant field by typing in the words Not set).
- Select Save and Test to confirm that the integration is configured properly.
Warning: Authorization Server requires a forward slash "/" at the end of the URL https://domain.halopsa.com/auth/
Congratulations, you've successfully connected your PSA!