RMM platforms (NinjaOne, Datto RMM, N-able)

Purpose

RMM connectors reconcile the device inventory, patch status and monitoring alerts already managed by your RMM platform against AssurIQ's asset and vulnerability model, avoiding duplicate agents and giving credit for patches applied outside AssurIQ.

Requirements

• An RMM tenant (NinjaOne, Datto RMM or N-able) with API access enabled for your account tier
• A dedicated API application/client with read-only or reporting scope
• Outbound HTTPS from the AssurIQ Cloud Connector to the RMM platform's API endpoint

Permissions

• Read-only API scope covering device inventory, OS and patch status
• Read access to monitoring alerts, where used for correlation
• No remote-control, scripting or ticketing write scopes are required or requested

Setup

1. 1
   Create an API application

   In the RMM platform's API/developer settings, register a new API application or client.
2. 2
   Restrict to read scopes

   Grant only device, inventory and patch read scopes; omit remote-access and scripting scopes.
3. 3
   Generate credentials

   Generate the client ID/secret or API key and store it in AssurIQ's Credential Vault.
4. 4
   Connect in AssurIQ

   In Integrations, select the RMM platform, paste the credentials and map organizations to AssurIQ customers.
5. 5
   Reconcile inventory

   Run the first sync and review the asset reconciliation queue for auto-merged and pending devices.

Verification

• Device counts from the RMM platform appear in the Asset Reconciliation queue
• Patch status from the RMM feed reduces duplicate findings in Vulnerability Center
• Organization-to-customer mapping is confirmed correct for every tenant

Data collected

• Device inventory, OS version and RMM agent health
• Patch and update install status
• Monitoring alerts relevant to endpoint health
• Organization/site structure for reconciliation

Security model

The API application is limited to read scopes; AssurIQ never issues remote commands or scripts through an RMM connector. Credentials are stored encrypted and traffic runs outbound over HTTPS.

Common errors

• AIQ-INT-001Integration disconnected
  The connector token expired or was revoked. Data from this system is stale.

Troubleshooting

• If devices appear duplicated, review the Asset Reconciliation queue and confirm matching keys (hostname, serial, MAC) are consistent between sources.
• If patch status conflicts with AssurIQ's own scan, the RMM feed and vulnerability scanner may sample at different times; the newer evidence wins.

Disconnect

1. Disconnect the RMM platform from AssurIQ Integrations.
2. Revoke or delete the API application/client in the RMM platform.