Integrations overview

Integrations connect us to the rest of your stack — PSAs for billing automation, security platforms for visibility, compliance tools for evidence. Most are partner-level (one configuration covers every client you onboard); a few are per-client (each of your clients has their own counterpart in the third-party tool, so each gets its own connection).

Where integrations live

• Settings → Integrations in your top-right partner menu. Partner-level: PSAs (ConnectWise Manage, Datto Autotask, HaloPSA), the Reporting API key generator, and similar partner-wide tools. Configure once, map each client to its counterpart on the other side.
• Per-client Tailor → Integrations under each client. For tools where the client has their own tenant — Drata, in particular. Each client gets its own setup.

Supported integrations at a glance

PSA integrations (billing automation)

Three PSAs sync user counts so your monthly invoicing stays accurate without manual intervention:

Integration	Sync cadence	Article
ConnectWise Manage	Nightly	ConnectWise PSA
Datto Autotask	Monthly (1st)	Datto Autotask PSA
HaloPSA	Nightly	HaloPSA

Each follows the same shape: create an API user/agent in the PSA, paste credentials into our integrations settings, map each INFIMA client to its PSA counterpart. The PSA then bills the right user count automatically as your client headcount changes.

Security & visibility platforms

• ConnectWise Security 360 — pushes training stats, phishing results, and the upcoming schedule into the Security 360 / Asio interface so the security team sees them alongside everything else. Configured in Asio with our server URL and Reporting API key.

Compliance evidence (per-client)

• Drata — pushes INFIMA training completion certificates to Drata as evidence against each framework’s training requirements (SOC 2, HIPAA, NIST AI, etc.). Configured per client under Tailor → Integrations since each client has their own Drata tenant.

External integrations (linked, not built-in)

A few partners use these by linking from their side; the setup happens in the other tool, not in ours:

• Acronis Cyber Protect — Acronis’s integration page describes how INFIMA security awareness training plugs into their platform.
• Lifecycle Insights — LCI’s step-by-step for enabling the INFIMA integration within their tool.
• vCIO Toolbox — vCIO Toolbox’s tools page; the INFIMA integration is configured from their side.

If you hit a snag setting any of these up from the external side, contact us — we can help diagnose, but the configuration steps themselves happen in the other vendor’s product.

What you’ll need before starting any PSA setup

Even though each PSA’s article walks you through specifics, the common ingredients across all three:

• Admin access to your PSA and an admin role in our app.
• An API account in the PSA that we can use to sync user counts. Most PSAs require you to create a dedicated API user/agent.
• A product / service / subscription record in the PSA that represents INFIMA’s offering at each client. This is what we update when user counts change.
• A contract / agreement / subscription per client that contains the INFIMA product. We map our clients to these.

The legacy step “create dedicated agreement and addition for INFIMA” is real in every case — the integration updates quantities, but the line item itself has to exist before we can update it.

Note

The exact terms differ per PSA — ConnectWise has Agreements and Additions, Autotask has Contracts and Contract Services, Halo has Subscriptions. The principle is identical: a line item exists, we update its quantity.

How client mapping works

After credentials are saved, you’ll see a list of your INFIMA clients on one side and a way to search/select the PSA counterpart on the other. For each client, pick the matching PSA company and the contract/agreement that holds the INFIMA line item.

Get this mapping right once — it’s how every future sync knows which PSA invoice to update for which client. A wrong mapping won’t break anything immediately but will send the wrong user count to the wrong customer.

Frequently asked

Can I use more than one PSA? Most partners use one. The integrations panel lets you connect multiple, but the workflow gets messier (different clients on different PSAs). If you’re migrating from one to another, connect both during the transition and unmap clients on the old one as you move them over.

What if a client isn’t in my PSA yet? Add the client (and their contract/agreement/subscription with our line item) to the PSA first, then come back and map. We can’t create PSA-side records for you.

Does deleting my PSA configuration delete client data on the PSA side? No — disconnecting only removes the credentials and mapping in our system. Records in your PSA (companies, agreements, additions/services/subscriptions) stay where they are. Reconnect later and you can re-map cleanly.

Why is Autotask monthly instead of nightly like the others? Autotask is billed on a monthly cycle. Our sync runs on the 1st of each month to update quantities for that month’s invoicing. The other PSAs accommodate nightly updates with pro-rata math.

A user was deactivated mid-month — does that show in billing? Depends on the PSA and your pro-rata settings. ConnectWise has a Prorate Agreement option that creates a partial-month adjustment. Autotask captures user count on the monthly sync. HaloPSA’s behavior depends on how you’ve set up your subscription billing rules.

Related

• Scheduled reports — the partner-level reporting cadence; PSAs handle invoicing, scheduled reports handle communication.
• Drata — the per-client compliance integration; pushes training completions as evidence into each client’s Drata tenant.