The Evo integration with Halo PSA simplifies synchronization between the two platforms — allowing you to import customers, align licensing data, and automate updates between Evo and Halo PSA. Companies can define unit costs and pricing for each license type, which are automatically created and updated within Halo PSA under the configured contracts.

With Evo and Halo PSA, you can:

Import customers from Halo PSA into Evo Security

Link existing Evo customers with corresponding Halo PSA accounts

Define unit cost and unit price for each Evo Security license type

Automatically create and update license details in Halo PSA under configured contracts

Synchronize license pricing bi-directionally between Evo and Halo PSA

Update license quantities in Halo PSA based on changes in Evo Security

Generate tickets or alerts within Halo PSA based on Evo events

Note: There is a new permission needed for roles to be able to manage the PSA integrations. Under Role-Based Permissions (On the Home Tab, select Access and Role-Based Permissions). The option to select for the appropriate role is "Manage PSA Integrations"

You can find the integration by navigating to Integrations on the Left side of your Evo Portal and selecting PSA and then HaloPSA

Configure Integration

To configure the PSA integration, you'll need to create a new Client ID and API key ( Secret ) for Evo to integrate with HaloPSA.

Note: An application with these privileges is required to perform this configuration correctly.

Permission Category	Access Level
Tickets	`read:tickets`, `edit:tickets`
Customers	`read:customers`, `edit:customers`
Contracts	`read:contracts`
Items	`read:items`, `edit:items`
Invoices	`read:invoices`, `edit:invoices`

Agent Permissions

To ensure the integration works correctly, the HaloPSA agent must have specific permissions enabled.

Where to configure agent permissions

In HaloPSA, go to Configuration → Teams & Agents → Agents.

Select the agent you want to update (or click New to create a dedicated integration agent).

In the agent’s navigation menu, click Permissions.

Apply the required permissions listed in the provided CSV (halo-agent-permissions.csv).

Important notes

Any permissions not included in the Table Below should be set to the negative / disabled option for that permission section (i.e., “No” / “Denied” / equivalent).

If you’re creating a new agent for this integration, we recommend using a dedicated integration agent (rather than a shared technician account) to make auditing and troubleshooting easier.

Permission Category	Access Level
Tickets Access Level	`Read And Modify`
Customers Access Level	`Read Only`
Users Access Level	`Ready Only`
Products Access Level	`Read and Modify`
Billing Details Access Level	`Read Only`
Invoices Access Level	`Read Create and Modify`
Customer Agreements 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 Re-assign Tickets	`Yes`
Editing of Actions	`Can Edit All Actions`
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 Ticket Types	`Yes`
Can View Item Costs	`Read and Modify`
Can View Item Prices	`Read and Modify`
Allow creation of new Ticket Types and linked objects	`Yes`

To Create API Credentials on Halo PSA, you will need to click “Configuration” on the home Page

Once in here you would then Click on “Integrations”

From here you will then click on “HaloPSA API”

Then once you are on the “HaloPSA API” Page, there will be a button that says “View Applications”. After clicking into View applications you will click “+New”

After clicking into View applications you will click “+New” at the top right

When creating an application, the Authentication Method should be "Client ID and Secret" This will generate the Client ID and Secret needed when configuring the integration with Evo. You will also need to set a name and an agent to login as

Retrieving the Base URI

Lastly, you will need to locate your Base URI, which can be found on the Halo PSA API page. This page displays both your Resource Server URL and Authorization Server URL.

For the Evo integration setup, use the base portion of either URL — omitting the suffix:

Remove /api from the Resource Server URL, or

Remove /auth from the Authorization Server URL

This resulting value is your Base URI, which will be entered in the Evo Portal during integration setup.

At this stage, you’ve gathered all the required details to configure and finalize the Halo PSA integration in the Evo Portal.

After entering the three required values obtained from Halo PSA, click Create to complete the integration setup. Once the integration has been created, you can proceed to configure synchronization settings for Companies, Billing, and Tickets within the Evo Portal

Billing Setup

Recurring Products (Item Group Configuration)

When the HaloPSA integration is first created, Evo licenses are automatically created as items within Halo. In order for these licenses to properly link to contracts and invoices, they must be assigned to an Item Group with a Group Type of Recurring Products.

Verifying or Creating the Recurring Products Item Group

Navigate to Configuration in HaloPSA.

From the left-hand navigation, select Items and Stock Control.

Click Item Groups.

Verify that an Item Group named “Recurring Products” exists.

If the Item Group does not exist:

Click + New in the top-right corner.

Create a new Item Group named Recurring Products.

Ensure the Item Group Type is set to Recurring Products.

Save your changes.

This step is required for Evo licenses to be billable through HaloPSA.

Recurring Invoices

As part of the HaloPSA integration, Evo automatically imports and links contracts (referred to as Agreements in Halo) to their corresponding companies. However, Evo licenses can only be billed when they are associated with a Recurring Invoice, which must be linked to the relevant agreement.

If a linked agreement does not have a recurring invoice, a warning will appear on the Integrations page stating:

“No recurring invoice associated with this contract.”

When this warning is present, billing for the affected company or contract will be disabled until a recurring invoice is created.

Creating a Recurring Invoice

Navigate to Invoices in HaloPSA.

Select Recurring Invoices from the left-hand navigation.

Click + New > New Recurring Invoice in the top-right corner.

Complete the required fields, ensuring:

The correct Customer is selected.

The appropriate Agreement (Contract) is linked.

Save the recurring invoice.

Once the recurring invoice is in place, Evo license billing will be enabled for the associated company and contract.

Ticketing Configuration Requirements

To enable ticket creation and automated workflows with the HaloPSA integration, several required ticket fields must be configured within HaloPSA. These fields are synchronized into the Evo portal and are used when defining ticket automation rules, including automatic ticket creation and closure.

The required ticket fields are:

Impact

Urgency

Category

Type

Impact and Urgency Configuration

Impact and Urgency values are managed within HaloPSA’s Lookup Codes and must exist prior to enabling ticketing automation.

Verifying Impact and Urgency Levels

Navigate to Configuration in HaloPSA.

Scroll to the bottom of the left-hand navigation and select Advanced Settings.

On the Advanced Settings page, scroll to the bottom and click Lookup Codes.

In the top-left dropdown menu, review the following lookup categories:

Impact Level

Urgency Level

Confirm that predefined values exist within both categories.

If no values are present, create the appropriate entries and save your changes.

These values will be automatically synced and made available in the Evo portal for ticket configuration.

Ticket Category and Type Configuration

Ticket Categories and Types are configured under HaloPSA’s ticket settings and are also required for automated ticket handling.

Verifying Ticket Types

Navigate to Configuration.

Select Tickets from the left-hand navigation.

Click Ticket Types.

Confirm that one or more ticket types are configured and active.

Verifying Ticket Categories (Category 1)

The Evo integration uses Category 1 values for ticket categorization.

From Configuration, remain in the Tickets section.

Navigate to Categorisation.

Click Edit Category 1 Values.

Verify that appropriate ticket category values are configured.

If needed, add or update category values and save your changes.

These Category 1 values will be synchronized into the Evo portal and used for ticket classification during automated ticket creation.

Once all required ticket fields are configured in HaloPSA, they will be available within the Evo portal for ticket automation and workflow setup.

Evo Support Bot