Datto RMM: connect, sync devices and alerts, map customers

Datto RMM is where your managed endpoints live. This connector reads two things out of it — each customer's device inventory and their open-alert counts — and hangs them off the matching Current company so they can feed your executive and CIO business reviews. It is read-only in the strictest sense: Current reads Datto RMM and can never change anything in it.

Datto RMM ships with the API switched off. Enabling it and creating a key are two separate admin actions, and both require a Datto RMM Administrator.

1. 1
   1 · Enable API Access

   In Datto RMM, go to Setup ▸ Global Settings ▸ Access Control and switch on Enable API Access. Until this is on, every key is rejected — this is the single most common reason a connection fails.
2. 2
   2 · Generate the API keys for a user

   Go to Setup ▸ Users, click the username the integration should run as (a dedicated service account is best practice, not a person who might leave), and choose Generate API Keys. Datto shows an Access key and a Secret key.
3. 3
   3 · Copy both keys now

   Copy the Access key and the Secret key before you leave the page — the Secret key is not shown again. If you lose it, regenerate the pair (which invalidates the old one).
4. 4
   4 · Note your platform/region

   Your Datto RMM URL tells you your platform — pinotage, merlot, concord, vidal, zinfandel, or syrah. Current needs it to reach the right API host, and it must match the region you log into.

1. 1
   Open the Datto RMM card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link), find the Datto RMM card in the Reporting integrations section, and paste your credentials.
2. 2
   Pick the platform, paste both keys

   Choose your platform/region from the dropdown, then paste the Access key into API Key and the Secret key into API Secret Key.
3. 3
   Press Test connection

   Current fetches a token from Datto live to prove the credentials work before storing anything. A bad key, a disabled API, or the wrong platform is rejected on the spot with the real reason. On success the keys are stored server-side only — the browser never sees them again.

The sync runs every 6 hours on its own, and Sync now covers the impatient path. Each run walks your account-wide site list, device list, and open alerts, then writes value-signals — never a raw event firehose.

Every request Current makes to Datto RMM passes through a read-only guard that only permits the specific GET endpoints above. The endpoints that change things — resolving or muting alerts, moving a device between sites, running a quick job, editing site variables, and especially resetting API keys — are not on the list and are unreachable, even by a code bug. Current cannot write to Datto RMM.

In Datto RMM a customer is a Site, identified by its siteUid. Current matches each site to one of your Current companies automatically by normalized name — lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped — and links it only when exactly one company matches. Anything it can't match confidently is left for you.

• ＋Unmatched sites appear on the Datto RMM card's mapping panel — press Map to pick the right Current company by hand.
• ＋A manual mapping is never overwritten by the auto-matcher on a later sync, and neither is a manual unlink.
• ＋Unmapped sites still sync — their devices and alerts are stored — but the data only appears on a company once the site is mapped to it.