PowerDMARC Autotask Guideline

PowerDMARC Support

Modified on: Fri, 31 Jul, 2026 at 5:30 PM

Overview

This guide walks you through connecting your Autotask PSA account to PowerDMARC. Once connected, you can map your customers to Autotask Companies, sync active domain counts to Autotask Contract Services in real time, and turn DMARC alerts into Autotask tickets — all from a single three-step wizard inside PowerDMARC.

Before starting, you need an Autotask account and admin access to create an API User. If you don't have Autotask yet, sign up at kaseya.com/products/autotask-psa.

1. Prepare Your Autotask Account

Before connecting PowerDMARC, complete this one-time setup inside Autotask. You need to create a dedicated API User and make sure your Contracts and Services are ready for mapping.

Create an API User

In Autotask, navigate to Admin → Resources (Users) → New API User. This user gives PowerDMARC secure access to your Autotask data and does not consume a paid resource license.

Fill in the following:

First Name / Last Name — Any clear identifier such as "PowerDMARC" / "Sync"
Email — Will be used as the API Username
Security Level — Select "API User (system)" for full API permissions
Secret — Generate or paste a Secret (this is the API password)

Warning

Autotask displays the Secret only once. Copy it immediately and store it securely. If lost, you must generate a new one.

Assign a Tracking Identifier

On the Security tab, assign a Tracking Identifier (Integration Code). Select "PowerDMARC" from the Vendor list if available, otherwise choose Custom (Internal Integration) — Autotask will auto-generate the code.

Once done, copy these three values:

Username — The API User's email address
Secret — The API password
API Integration Code — The Tracking Identifier from the Security tab

Set Up Contracts and Services (if using billing sync)

If you plan to use billing sync, make sure each customer you want to map has an active Contract in Autotask with at least one Service attached. PowerDMARC will use these to track billable domain counts.

Contract — The billing agreement between you and your customer (e.g., "Acme Corp – Managed Services Agreement"). Contracts are created per-Company in Autotask under Admin → Contracts
Service — A billable line item added to a Contract. This is what PowerDMARC updates with your customer's active domain count. Set the unit price on the Service to reflect your per-domain rate

Note	If you're using billing sync but a Company doesn't have a Contract or Service ready, PowerDMARC will show a warning during mapping and give you a direct link to Autotask so you can add one.

2. Open the Autotask Integration in PowerDMARC

Log in to PowerDMARC and navigate to Integrations from the left sidebar. Find the Autotask card and click Connect to Autotask to launch the three-step setup wizard.

3. Step 1 — Connection

Enter the three credentials you copied from Autotask:

Username — Your API User's email address
Secret — The API password
API Integration Code — The Tracking Identifier

Click Connect & Continue. PowerDMARC will automatically detect your Autotask zone, verify your credentials, and move you to Step 2.

Note	If the connection fails, verify that your API User is active in Autotask and that all credentials were copied correctly. Zone detection is automatic — you don't need to specify a webserver URL.

4. Step 2 — Customer Mapping

Link each PowerDMARC account to the corresponding Autotask Company. This is also where you decide whether PowerDMARC should manage billing in Autotask.

Enable Billing Sync (optional)

At the top of Step 2, toggle Enable billing sync on or off:

ON (default) — PowerDMARC tracks active domain counts against Autotask Contract Services. Mapping table shows 4 columns: MSSP Account, Autotask Company, Autotask Contract, Autotask Service
OFF — PowerDMARC only automates ticket creation — no domain counts are synced. Mapping table shows 2 columns: MSSP Account, Autotask Company

Complete the Mapping

For each customer, select the values in each column of the mapping table left-to-right:

MSSP Account — Select the account from your PowerDMARC platform
Autotask Company — Select the matching Autotask Company
Autotask Contract — Select the Contract under that Company. Available Contracts are filtered based on the selected Company
Autotask Service — Select the Service within that Contract. Available Services are filtered based on the selected Contract

Use + Add New to add rows manually, or + Add All Customers to pre-populate a row for every account. Use Resync at any time to refresh the list of Companies, Contracts, and Services from Autotask — existing valid selections are preserved.

Note	Contracts and Services must be created in Autotask before mapping. The selected Service will track the number of billable domains per customer. If a Company doesn't have Contracts yet, click Go to Autotask, create one, then click Resync.

Behind the scenes, PowerDMARC keeps your Contract Services updated automatically whenever a domain is added, removed, or moved between customers. No manual reconciliation needed — Autotask records every change as a Contract Service Adjustment so you have a full audit trail.

Warning

Autotask generates billing periods forward. Domain changes made mid-month are reflected in the next billing period — the current period's invoice is not retroactively re-priced. This matches standard MSP billing practice.

When finished, click Next to continue to Step 3.

5. Step 3 — Map Alerts to Tickets

Choose which DMARC alerts should automatically create tickets in Autotask, and set the ticket options for each customer.

Note	Only customers and domains with associated alert configurations in PowerDMARC are displayed here. Completing this step does not create any tickets immediately — tickets are only created when a live alert fires.

Click the arrow next to a customer to expand their configuration, or use Expand All to open all customers at once. Use the search bar to filter by customer name or domain.

For each customer, configure the following:

Ticket Category — Required. Determines the ticket type in Autotask
Queue — Required. Determines routing inside Autotask
Location — Optional. Filters the End User dropdown
End User — Optional. The Autotask Contact listed on the ticket

Then select which alert types and domains should trigger ticket creation — DNS Alerts, Threshold Alerts, and Forensic Alerts. You can select all domains for an alert type at once, or choose individual domains.

Note	Ticket configuration data (Categories, Queues, Locations, Contacts) refreshes automatically every hour to stay up to date with your Autotask setup. You can also click Resync per customer to refresh immediately.

Note	If your chosen Ticket Category has required custom fields (UDFs), ticket creation will fail. Either choose a Ticket Category without required custom fields, or make those fields optional in Autotask.

When finished, click Submit to Autotask. This completes the initial setup.

6. Integration Summary

After submitting, you are taken to the Autotask integration overview page. A success notification confirms that all configurations and mappings have been submitted to Autotask.

The summary shows three status cards at a glance:

Connection — Confirms your Autotask instance is authenticated and active
Customers — Number of accounts successfully mapped to Autotask Companies
Alerts — Number of alert types enabled for automatic ticket creation

Click Edit on any card to return to that step of the wizard and make changes. You can update your configuration at any time from Integrations → Autotask.

7. Where to See Billing in Autotask

Once billing sync is enabled and Step 2 is complete, PowerDMARC updates your Contract Services in real time. Here's where to verify everything is working:

Company → Contracts tab — Shows all Contracts under that Company. Open the mapped Contract to see the Service PowerDMARC is updating
Contract → Services tab — Shows the Service with the current unit count matching your customer's active domain count in PowerDMARC
Company → Billing tab — Shows aggregated revenue for that Company, including revenue from PowerDMARC-managed Contract Services. Values appear as Pending Revenue (upcoming periods) and Posted Revenue (billed periods)

Note	If Revenue shows $0 immediately after setup, it's because billing periods haven't been posted yet. Autotask generates periods on the Contract's schedule — revenue will populate once the first period posts.

8. Access Control

The Autotask integration is available to MSSP accounts where the Autotask Integration toggle is enabled in account settings. Users must also have the Access Autotask Integration permission assigned to their role. By default this is granted to MSSP Owner and MSSP Admin roles, and can be extended to custom roles from role management settings.