PSA Integration Features

PSA Integration Features

DMARCER connects to leading Professional Services Automation (PSA) platforms, so you can manage domain security from inside the tools your team already uses. Once a PSA is connected, the integration helps you in four areas: linking your DMARCER customers to their PSA records, syncing domains into the PSA as assets, opening tickets for DMARCER alerts, and keeping billing quantities in step with your live domain counts. PSA integration is included on some plans. If the Configure and customer-link options are not showing, your plan may not include it yet, and DMARCER will let you know rather than quietly doing nothing. If you would like it added, please get in touch and we will be happy to help.

We aim to give you a consistent experience across every connector, but each PSA offers different capabilities, so a few areas are only available on some platforms.

Feature support by PSA

The table below shows the features supported by each PSA integration today. Autotask and ConnectWise are in progress, and we will switch features on as each one goes live.

• Halo PSA: customer link, asset sync, alert tickets and billing are all supported.
• SuperOps: customer link, alert tickets and billing are supported. SuperOps does not let DMARCER create asset records, and SuperOps tickets are linked to the client only, not to an individual asset.
• Autotask and ConnectWise: these connectors are built and we are getting them ready for their first live test. Autotask also offers a customer-type filter, so you can narrow down the client picker.

Step 1: connect the PSA and link your customers

You connect the PSA on the Integrations page, the same way you add any integration. Once the connection shows as active, the integration's three-dot menu gives you two PSA-specific options: Manage customer links and Configure. Start by linking customers, because the asset, alert and billing areas all work per linked customer. Nothing flows through until a DMARCER customer is linked to a PSA client.

Open Manage customer links from the three-dot menu to handle links for the whole integration. The window has two tabs: Linked here shows the DMARCER customers already linked to this PSA, and All PSA clients lets you search the full list of clients in your PSA. Find the PSA client you want, then either link it to an existing DMARCER customer or, if there is no matching DMARCER customer yet, use the create-and-link option to add a DMARCER customer from the PSA record and link the two in one step. Each customer's Overview tab also has a PSA links card that lists the links it already has and brings you back here to set up new ones.

The Reference column shows the PSA's own id for each client, which is handy when several clients share a similar name. On Autotask, a customer-type filter appears next to the search box (for example, to hide Leads or Prospects and show only Customers). It is hidden on connectors that do not use customer types.

A DMARCER customer can be linked to only one PSA customer across all your integrations. If you try to link a customer that is already linked elsewhere, DMARCER will let you know where it is linked so you can unlink it there first, then link it here. Unlinking only removes the connection inside DMARCER: the record in your PSA is never changed or deleted. Re-linking to the same client is safe and simply refreshes the saved name and the last-verified time. There is also a Refresh option, in case the name has been edited on the PSA side.

Step 2: asset sync (push domains into the PSA)

Open Configure from the integration's three-dot menu to reach the Assets, Alerts and Billing tabs. On the Assets tab, tick Enable Asset sync to push your DMARCER domains into the PSA as assets and keep them up to date. Set a Sync cadence, choose the asset template the assets should be created under, and match your DMARCER fields to the template's fields. For each field you can either map a DMARCER field or set a default value in the panel below. If the template needs a field that is neither mapped nor given a default, the PSA will not be able to create the asset, so do check the field list before syncing. You can create a missing field straight from a mapping row, and Reload fields fetches the template's field list again.

Use Sync now to run an immediate one-off push of every linked customer's domains. For each domain, DMARCER first looks for an existing PSA asset that matches the domain name and links to it if it finds one, otherwise it creates a new asset from your field mappings. It never creates duplicates and never deletes assets from the PSA. The confirmation message tells you how many were created, matched, updated, unchanged or failed. Force re-push will re-process assets that DMARCER would normally skip; leave it switched off for everyday runs.

On SuperOps, asset categories and types are set up inside SuperOps itself (Settings, then Assets), and DMARCER reads them into the template picker. DMARCER cannot create new SuperOps asset templates from the integration.

Step 3: alerts (open tickets for DMARCER alerts)

On the Alerts tab, tick Open tickets for DMARCER alerts. From then on, when DMARCER raises an alert it creates a ticket in this PSA and keeps track of it, so it can update or resolve the ticket as things change. Set the status to use when a ticket is created and the status to use when the issue fixes itself, and, if you like, choose a default team and ticket type. The severity-to-priority settings let you set a PSA priority for info, warning and critical alerts; leave any of them blank to use the PSA default. The Subject template controls the ticket title and supports the tokens {AlertTitle}, {Domain} and {Severity}.

Which kinds of alert actually open tickets is chosen separately, under Alerts, then Settings, and that choice applies across your whole account. Tick Push to PSA next to each alert kind you want sent to your PSA. If you have more than one PSA connected, a ticked alert opens a ticket in all of them, which keeps things simple. Use Send Test Ticket on the Alerts tab to send a clearly-marked test all the way through the live connection. It uses the first linked customer and your last-saved Alerts settings, so save the form before you test. If the test fails, DMARCER tries again while leaving out one optional field at a time, and tells you which field the PSA would not accept. Remember to close the test ticket in the PSA afterwards.

Step 4: billing (align quantities with domain counts)

On the Billing tab, tick Align billing to push the live domain count onto each customer's linked contract line. Choose a cadence of Daily or Monthly; for Monthly, set a Day of month between 1 and 28 (sticking to 1 to 28 avoids the awkward end of February, and if a scheduled date is missed, DMARCER catches up at the next run). The per-rule defaults (whether to bill or skip, and whether to count Aggregate or Per-asset) are used as the starting point for each new customer rule, and every rule can change them.

You set the billing approach for each customer using the Billing button on the customer link. The choices are: Combined - Total (all domains on one line); Combined - Per-Kind (Standard and Parked domains on two separate lines); Separated (DMARCER manages one line per domain); Per-Asset (the asset itself is linked directly to the contract); and Don't bill (skip this customer and record it as skipped). For each approach you pick the contract and line the quantity should go to, and you can create a new line there and then from the contract. DMARCER sends the quantity as an update to the linked line, and never overwrites figures it does not manage.

The Per-Asset approach uses the PSA's own per-asset contract linking, so it needs Asset sync switched on and a connector that supports it. It is available on Halo PSA only and is hidden or greyed out elsewhere. If the option is not available, turn on Asset sync on the Assets tab first.

Common pitfalls

• PSA integration is included on some plans. If the Configure and customer-link options are missing, or you see a message that the feature is not on your plan, your plan may not include it yet. Get in touch and we will help.
• Nothing syncs until customers are linked. Asset sync, alert tickets and billing all work per linked customer, so link the customer first.
• One DMARCER customer links to one PSA customer across every integration. To move a customer to a different PSA, unlink it first, then link it again.
• Asset creation fails if the template needs a field that is neither mapped nor given a default value. Check the field mappings before you run Sync now.
• On SuperOps, asset templates are set up inside SuperOps (Settings, then Assets), and tickets link to the client only, not to an individual asset.
• Per-Asset billing needs Asset sync turned on, and is available on Halo PSA only.
• Send Test Ticket uses your last-saved Alerts settings, so save the form before you test, and remember to close the test ticket in the PSA.
• With more than one PSA connected, an alert ticked for Push to PSA opens a ticket in every connected PSA.