HaloPSA
HaloPSA Integration Guide
Introduction
HaloPSA Integration will allow you to create issues with the detailed data per customer when the action will be called.
Prerequisites
A HaloPSA Agent account with required privileges.
API credentials (Application) with required permissions.
Required Privileges for Agent Account
Tickets Access Level
Read and Modify
Clients Access Level
Read Only
Users Access Level
Read Only
Assets Access Level
Read Only
Can add new Tickets
Yes
Can edit closed Tickets
Yes
Can view Unassigned Tickets
Yes
Can view Tickets that are assigned to other Agents
Yes
Can change a Ticket's Ticket Type
Yes
Can Re-assign Tickets
Yes
Can Edit Advanced Ticket Details
Yes
Editing of Actions
Can Edit Own Actions Only
Can assign to Agents in Teams the Agent is not a member of
Yes
Can Edit Tickets Which Are Not Assigned To Them
Yes
Can always update Ticket Statuses and re-assign Tickets outside of actions
Yes
Allow use of all Asset Types
Yes
Allow use of all Ticket Types
Yes
Allow use of all Asset Fields
Yes
Required Permissions for API Credentials (Application)
read:tickets
Read tickets that are opened by perimeters
edit:tickets
Create and update tickets
read:customers
Read Customer Inventory
read:assets
Read Asset Inventory
read:projects
Read Projects
all:teams
Read Teams and Members
Onboarding HaloPSA in your Perimeters account
Go to Integrations → Response and Automation → Select "HaloPSA" -> Click "+ Add" -> Click "+ Start Integration".
"Namespace" - Fill in the domain name for your HaloPSA instance. For example, if your HaloPSA domain name is "perimeters.halopsa.com" you would enter "perimeters" in this field.
"Client ID" - Provide the Client ID that was create in earlier steps.
“Client Secret” - Provide the Client ID that was create in earlier steps.
Click "Finish" to complete the onboarding process.
Once you have completed these steps, HaloPSA should be successfully integrated with your Perimeters account.
Last updated