Connecting SuperOps

SuperOps is one of the PSA tools DMARCER can connect to. Once it is connected, DMARCER can raise email-security findings as SuperOps tickets and push your live domain counts onto your billing contracts, so domain-security risks show up right inside the tools your team already uses every day. (SuperOps discovers assets through its own monitoring, and it does not let outside tools create assets, so DMARCER does not add your domains into SuperOps as assets and the Assets tab is hidden for SuperOps connections.) SuperOps uses a single API token rather than the sign-in flow some other PSAs use, which makes it quick to set up.

Before you start

PSA integration is included on some plans. If you do not see the PSA options when you try to add the integration, your plan may not include it yet, so please get in touch and we will help. You will also need the Integration management permission (your account administrators always have this). Have these three SuperOps details ready before you begin.

• API token: in SuperOps, go to Settings, then My Profile, then API token, and generate a token.
• Subdomain: this is the portal slug only, for example acme from acme.superops.ai. It is shown under Settings, then MSP Information. Enter just the slug, not the full web address.
• Data centre: whether your SuperOps account is hosted in the US (api.superops.ai) or the EU (euapi.superops.ai). Choosing the wrong one will stop the connection from working.

Step 1: Add the integration

• Open Integrations and start a new integration.
• In the provider dropdown choose SuperOps. The fields for your SuperOps details then appear.
• Enter your API token, your Subdomain (the slug) and pick your Data centre (US or EU).
• Give the connection a Friendly name. This is required, and it is how you tell this integration apart from your others, so pick something you will recognise.
• Decide whether to start in Test mode. You can switch between Test and Live at any time from the integration card; switching resets the connection status until you test again.
• Save to create the integration.

[Screenshot: the Add integration dialog with SuperOps selected, showing the API token, Subdomain and Data centre fields]

Your token is encrypted before we store it and is never written into any logs. As soon as you save, DMARCER runs a connection test automatically, so you get instant feedback.

Step 2: Confirm the connection

The connection test does a small, read-only check against SuperOps (it simply looks up a single client) to confirm both your token and your subdomain are valid. A healthy result shows Connected. If it does not work, you will see one of two clear messages that point straight at the cause:

• Token rejected: SuperOps would not accept the token. Regenerate it in Settings, My Profile, API token, then update your details in DMARCER.
• Request rejected: this is usually an invalid subdomain. Double-check that you entered the portal slug only, for example acme, and not the full web address.

You can re-run the test at any time from the integration card. If you ever need to change the token, subdomain or data centre, use Manage credentials; when you save there, the status goes back to Untested and a fresh test runs.

Step 3: Link your customers

From the integration's action menu, choose Manage customer links. Search for a SuperOps client by name and link it to the matching DMARCER customer. This link is what tells DMARCER which SuperOps client a domain's tickets and billing belong to, so be sure to link every customer you want to sync.

Step 4: Configure alerts (tickets)

Choose Configure from the action menu to open the configuration dialog. For SuperOps this opens on the Alerts tab. Tick Open tickets for DMARCER alerts to turn ticket creation on, then set how those tickets should look:

• New status: the SuperOps status applied when DMARCER opens a ticket.
• Self-heal status: the status DMARCER moves the ticket to once the underlying problem clears, for example after a misconfiguration is fixed and re-checked.
• Team and Ticket type (category): the SuperOps technician group and category the ticket is filed under. These dropdowns are filled in from your SuperOps account.
• Severity to priority mapping: match DMARCER's Info, Warning and Critical levels to SuperOps priorities, or leave them on the PSA default.
• Subject template: the wording used for the ticket subject, for example DMARCER: {AlertTitle} - {Domain}.

Which kinds of alert actually open tickets is set separately, and applies across your whole account, under Alerts, then Settings. Tick Push to PSA against each kind of alert you want to flow through. Please note: if you have more than one PSA integration, a ticked alert opens a ticket in all of them. This is intentional, to keep things simple. There is also a test-ticket button on the Alerts tab that uses your last saved settings against the first linked customer, so save the form before you test.

Step 5: Billing (optional)

On the Billing tab, tick Align billing to push the live domain count onto each customer's linked contract line. Set how often this runs (Daily, or Monthly on a day of the month you choose) and the defaults for each rule: whether new rules bill or skip, and the default level of detail (Aggregate, one rolled-up quantity per rule, or Per-asset, one line for each linked domain). You then match each linked customer to one or more SuperOps contract lines from Manage customer links, using the Billing button against the customer, where a customer can have separate rules for Total, Standard and Parked domain counts. DMARCER only sends the quantity; the rate stays in your SuperOps service catalogue. You create any new contract lines in SuperOps first and then pick them here, because SuperOps does not let the integration create contract lines for you.

Common pitfalls

• Subdomain confusion: this is the most common reason a connection is rejected. Enter the slug only (acme), never the full acme.superops.ai address or a web link.
• Wrong data centre: a US token will not work against the EU connection, and the other way round too. Pick the region your SuperOps account is actually hosted in.
• No asset sync: SuperOps discovers assets through its own monitoring, and it does not let outside tools create assets. Because of this, the Assets tab is hidden for SuperOps connections and DMARCER does not add your domains into SuperOps as assets. If you need a domain shown as an asset, create it in SuperOps first (Assets, then Add).
• No tickets appearing: check that the customer is linked, that the customer has a domain, that Open tickets for DMARCER alerts is ticked, and that the relevant kind of alert has Push to PSA turned on under Alerts, then Settings.
• Ticket creation blocked by SuperOps rules: some SuperOps accounts make certain fields, such as request type, mandatory in their ticket settings. If a ticket fails to create, use the Send Test Ticket button on the Alerts tab, which shows you the exact SuperOps error, including the field that is causing the problem. Ticket failures are also recorded in the audit log.
• Plan or permission: if the PSA options are missing altogether, your plan may not include the integration, so get in touch. If every action returns a permission error, you do not yet have the Integration management permission.