PowerDMARC Now Integrates With HaloPSA

PowerDMARC now connects natively with HaloPSA. Allowing MSSPs and MSPs to link their HaloPSA instance to PowerDMARC in minutes, mapping customers, syncing subscription quantities automatically, and routing DMARC alerts straight into their service desk as tickets.

The integration joins the growing list of PowerDMARC integrations built specifically for partner workflows.

What Is HaloPSA?

HaloPSA is a professional services automation platform built for MSPs and IT service providers. It brings ticketing, billing, asset tracking, and client management together in one place, giving service teams a single system to run their day-to-day operations from.

What the PowerDMARC-HaloPSA Integration Does

The PowerDMARC HaloPSA integration covers customer mapping, subscription billing, and alert handling. It is designed to remove the repetitive admin work that sits between your DMARC service and the systems your team actually operates in. Here’s what you can expect from the integration:

Secure connection

You connect using your own HaloPSA API credentials (Client ID and Secret), generated inside your HaloPSA environment. Access stays scoped to your instance and fully under your control, without any shared keys or third-party broker in the middle.

Customer mapping

Link each PowerDMARC customer account to its corresponding HaloPSA client. Once mapped, the platforms stay in sync: when a customer’s domain list changes in PowerDMARC, those changes flow into HaloPSA automatically, helping your client lists stay aligned across both platforms.

Subscription sync

PowerDMARC tracks active billable domains for every mapped client and updates the HaloPSA subscription quantity in real time.
For partners managing hundreds of customers, month-end has historically meant pulling domain counts from PowerDMARC, comparing them against the last cycle, and editing subscriptions client by client, which requires hours of error-prone work.

With automatic sync, the subscription quantity in HaloPSA is always current, and your invoicing reflects the actual service delivered without anyone touching a spreadsheet.

Alert-to-ticket

Choose which DMARC alert types should create tickets in HaloPSA, such as:

DNS changes to DMARC, SPF, or DKIM records
Threshold breaches when email failure volumes spike
Forensic (RUF) reports, and more

When any mapped alert gets triggered, a ticket lands in your service desk with the full alert details attached, ready for your team to act on.

This matters because DMARC alerts delivered to a shared mailbox tend to be assessed late or missed entirely during periods of high ticket volume. Routing them directly into the queue your analysts already work from means SLAs apply, ownership is clear, and nothing sits unread.

How to Set Up the PowerDMARC-HaloPSA Integration

Setup happens in two parts: a short one-time configuration inside HaloPSA to generate API credentials, followed by a three-step wizard inside PowerDMARC.

Step 1: Prepare HaloPSA access

Before connecting to PowerDMARC, you need to create a dedicated API agent and an API application inside HaloPSA.

Create an API agent

Go to Configuration → Teams & Agents and click New Agent.
Enable the “Is an API-only Agent” toggle. This ensures the account does not consume a license seat, and every auto-created ticket is clearly attributable to the integration in audit logs.
Save the agent.

Then, under Permissions, assign the following access levels to the agent:

Ticket Access Level – Read and Modify
Clients Access Level – Read Only
Users Access Level – Read Only
Items Access Level – Read Only
Software Licensing Access Level – Read and Modify
Can Add New Tickets – Yes

These permissions are required for reading customers and items, creating and updating subscriptions, and creating tickets from alerts.

Create the API application

Go to Configuration → Integrations → HaloPSA API → Applications and click New.
Select Client ID and Secret (Services) as the authentication method.
Set Login Type to Agent, and select the API-only agent you just created.
Copy the generated Client ID and Client Secret and store them securely — you’ll need them to connect the integration in PowerDMARC.

Note: HaloPSA only shows the Client Secret once. If lost, you’ll need to regenerate it and re-enter it in PowerDMARC.

Finally, under Permissions for the application, assign the following scopes:

read:customers
edit:customers
read:softwarelicensing
edit:softwarelicensing
read:tickets
edit:tickets
read:items

Step 2: Connect HaloPSA to PowerDMARC

In PowerDMARC, go to Integrations → HaloPSA and click Connect to HaloPSA to launch the three-step wizard.

On Step 1: Connection, enter:

Base URL: Your HaloPSA instance URL (e.g., https://yourcompany.halopsa.com)
Client ID: Generated during application creation
Client Secret: Generated during application creation

Ensure all values are entered exactly as provided to prevent connection errors. Click Connect & Continue to move to Step 2.

Step 3: Map customers and items

On Step 2: Customer & Item Mapping, link each PowerDMARC customer account to its corresponding HaloPSA customer, and select the HaloPSA item that will be used to create the subscription for that customer.

Make sure all items are created in HaloPSA beforehand, as these will be used to link to subscriptions.

Subscription notes:

One subscription is created per mapped customer.
Ensure all domains under a customer account share the same billing date — mismatched dates within an account can cause billing inconsistencies in HaloPSA.

Once all mappings are configured, click Next to continue.

Step 4: Map alerts to tickets

On Step 3: Alert-to-Ticket Mapping, configure which DMARC alerts should automatically create tickets in HaloPSA.

Only customers meeting both of the following conditions will be displayed:

They were mapped in Step 2.
They have at least one alert configuration in PowerDMARC.

For each displayed customer, select the alert configurations and domains for which tickets should be generated. Tickets will be created automatically whenever alert logs are received based on the mapped configurations.

Per-customer ticket options:

Ticket Type – required
Site – optional
End User – optional (only available after a Site is selected)

Once finished, click Submit to HaloPSA to complete the initial setup. You can update any of these configurations later from Integrations → HaloPSA.

For step-by-step instructions on how to navigate the integration, refer to the full HaloPSA setup guide.

Who Can Use It?

The HaloPSA integration is available to MSSP accounts that have the HaloPSA Integration toggle enabled in account settings. Users also need the Access HaloPSA Integration permission on their role. This is granted by default to MSSP Owner and MSSP Admin roles and is extendable to custom roles from the role management tab.

It’s a fit for any partner already standardised on HaloPSA as their PSA, whether you’re delivering DMARC as a standalone managed service, bundling it into a broader email security offering, or running it as part of a wider cybersecurity practice. The integration is built to slot into the workflows your team already runs in HaloPSA rather than asking them to learn another tool.

If you’re an MSP or MSSP using HaloPSA and the toggle isn’t yet enabled on your account, reach out to your PowerDMARC account manager. Not yet a partner? Learn more about the PowerDMARC MSP and MSSP program.

Get Started

If you’re already on HaloPSA, you can connect it to PowerDMARC and stop reconciling domains by hand from the next billing cycle. Start a free trial or contact our team to enable the integration on your account.

About
Latest Posts

Ahona Rudra

Domain & Email Security Expert at PowerDMARC

Ahona is the Marketing Manager at PowerDMARC, with 5+ years of experience in writing about cybersecurity topics, specializing in domain and email security. Ahona holds a post-graduation degree in Journalism and Communications, solidifying her career in the security sector since 2019.

PowerDMARC Now Integrates with HaloPSA