Best Practice: Review the 'Least Privileges for HaloPSA” on configuring security for the API so it does not use full admin rights. Least Privileges for HaloPSA Integration
Overview
Scan results are sent as tickets to HaloPSA, with options for Company syncing to inform teams of scan alerts/results.
The HaloPSA integration has 2 main integration points.
Company Syncing - keep your companies synced between ConnectSecure and HaloPSA. You can import directly from HaloPSA or map an existing ConnectSecure company to a HaloPSA company. This ensures any alerts/tickets raised are going to the correct company.
Create Ticket - enable ticketing integration using your defined Event Set and Integration Profile settings. This is optional and is not required to use Company Syncing options.
Getting Started
Navigate to Global > Settings/Integration > tap on the HaloPSA tile.
Setup
NOTE: If you are using Actions in HaloPSA to update tickets, you may need to consider the Private note settings to allow ticket updates from workflows.
Credentials
Complete the required fields and tap Update to continue:
Name: Give the integration creds a name of your choice.
Client ID: Enter the HaloPSA Client ID.
Client Secret: Enter the HaloPSA Client Secret.
Domain: Enter the HaloPSA domain. Do not include https or /API at the end of the name.
Tenant Name: Enter the HaloPSA tenant name.
Authorisation Server: In HaloPSA, click Configuration > Integrations > HaloPSA API to view your Resource Server, Authorisation Server, and Tenant Name.
Associated Company: You can leave this blank to use for all companies.
Event Set
Tap on the Event Sets KB to see full information: https://cybercns.atlassian.net/wiki/x/UYCugg
Integration Rules
Here, you define how the ticket is created in HaloPSA and which parameters are applied to the ticket upon creation. Complete all required fields and tap Save to continue.
The red highlight cell indicates a Required field.
Required Fields Indicated |
Field | Description / General Use |
|---|---|
Name | Set the name of the Integration Profile. We recommend separating them based on the ticket's ‘Priority’ so you have a profile for your P1, P2, and P3 tickets, and so on. |
SLA For Ticket Creation | Select the SLA from HaloPSA configured options. |
Priority For Ticket Creation | Select the Priority based on your HaloPSA configured options. |
Ticket Type For Ticket Creation | Select the Ticket Type based on your HaloPSA configured options. |
Status For Ticket Creation | Select the Open Status based on your HaloPSA configured options. |
Status For Ticket Close | Select the Closed Status based on your HaloPSA configured options. |
Team For Ticket Creation | Select the Team based on your HaloPSA configured options. |
Agent For Ticket Creation | Select the Agent based on your HaloPSA configured options. |
Client For Ticket Creation | Select the Client based on your HaloPSA configured options. |
User For Ticket Creation | Select the User based on your HaloPSA configured options. |
Category For Ticket Creation | Select the Category based on your HaloPSA configured options. |
Urgency For Ticket Creation | Select the Urgency based on your HaloPSA configured options. |
Impact for Ticket Creation | Select the Impact based on your HaloPSA configured options. |
Event Set | Select the associated Event Set from ConnectSecure. This is the association the Event Set uses when creating tickets. |
Company Mapping
This is where you manage your company mappings between HaloPSA and ConnectSecure; you can import them directly from HaloPSA or map existing ConnectSecure companies to HaloPSA companies using the Add button. These mappings also include what Event Set and Integration Profile settings apply to the company when using the Create Ticket option.
Upon saving, the Selected Companies section appears with your mapping selection(s). You can use the three-dot action menu to Edit or Delete the company mapping and settings.
Create Ticket = This will enable automatic ticket creation for the selected company based on the mapped Event Set and Integration Profile settings. Enable Configuration is not required or linked to this.
NOTE: If you are using Actions in HaloPSA to update tickets, you may need to consider the Private note settings to allow for ticket updates from workflows.
Get Support
If you have an integration-related inquiry, please email support@connectsecure.com with the details, and our Support Team will assist you.