What lands on the client
Device inventory and OS build, device health and pending reboot, patch status with pending patches by NinjaOne severity, antivirus and EDR status, BitLocker on the Windows system drive, software, and alerts.
Live RMM integration
NinjaOne device posture on the client record.
Scopable connects to NinjaOne with read-only access and puts device health, patch status, antivirus and EDR status, and BitLocker encryption on the clients you already have.
Built for MSPs that run NinjaOne and need endpoint posture attached to the right client before a QBR, an assessment, or a compliance review.
Exact supported scope
Read posture without touching the RMM.
The integration reads with NinjaOne's Monitoring scope and keeps NinjaOne as the source of device truth. The setup guide documents every step.
Compliance evidence
Patch status and pending patch counts, antivirus and EDR status, BitLocker encryption, installed software, and active alerts feed GRC evidence. Unknown values read as needs review, never as clean.
Client mapping
Each NinjaOne organization links to a client you already have. Exact name matches link, the rest are suggested, and nothing creates a client.
Freshness
Scopable syncs every 4 hours. Security data older than 14 days shows as stale, and a device that never reported shows as not collected.
Data-flow proof
From a NinjaOne organization to client evidence.
Connection and mapping are separate steps. Devices only sync for organizations you link to a client, so one customer's fleet never lands on another.
Create a Monitoring API client
In NinjaOne, add an API Services app with the Client Credentials grant and the Monitoring scope only.
Connect and check
Pick your NinjaOne region, paste the client ID and secret, and connect only after the check returns your organizations.
Map organizations
Link each NinjaOne organization to an existing client, or exclude it. Devices only sync for linked organizations.
Preview and sync
Preview what the first sync would create, update, and hold back, then start it. Scheduled syncs follow every 4 hours.
Use the posture
Review devices on the client's Configurations tab and the evidence they feed in GRC before a review or audit.
Limits
What the NinjaOne integration does not do.
The integration is read-only. Patching, remediation, and remote actions stay in NinjaOne.
Devices in organizations that are not linked to a client do not sync.
A missing value is shown as not collected or unknown, never as clean. Mac and Linux devices show disk encryption as unknown.
Device health, patch severity, OS build, and pending reboot are shown on the client but are not scored as compliance evidence.
Security review
What the technical validator should check.
The API client is the whole access boundary. Keep it Monitoring-only and treat the secret like any other RMM credential.
- Create a dedicated NinjaOne API client for Scopable so it can be rotated on its own.
- Select the Monitoring scope only. Leave Management and Control off.
- Keep the client secret out of tickets, chats, and screenshots.
- Confirm the region matches the NinjaOne address your account signs in on.
- Review organization mappings before relying on posture in a client meeting.
Buying path
Decide here, configure in the setup guide.
Use this page to validate fit and limits. Use the docs when an admin is ready to create the API client and map organizations.
NinjaOne setup guide
Use this for the API client, region, organization mapping, first sync, freshness, and troubleshooting.
Read the setup guideIntegrations hub
See where RMM data fits beside PSA, Microsoft, distributor, and documentation sources.
See all integrationsMSP GRC and compliance software
See how device posture becomes evidence in client compliance work.
See the GRC workflowNinjaOne questions
What NinjaOne data does Scopable read?
Device inventory with OS build, device health and pending reboot, patch status with pending patches by NinjaOne severity, antivirus and EDR status, BitLocker on the Windows system drive, installed software, and active alerts for devices in organizations linked to a client.
Can Scopable change anything in NinjaOne?
No. Scopable uses NinjaOne's Monitoring scope only. It writes nothing to NinjaOne and never runs a remote action on a device.
Which NinjaOne data feeds compliance evidence?
Patch status and pending patch counts, antivirus and EDR status, BitLocker encryption, the installed software list, and active alerts. Device health, patch severity, OS build, and pending reboot land on the client for review.
Does NinjaOne replace my PSA?
No. NinjaOne runs beside Connectwise or Halo. Your PSA keeps owning clients, and Scopable never creates a client from a NinjaOne organization.
Can I run NinjaOne and another RMM on the same client?
Yes. Each source keeps its own record of a device. Devices match on serial number first, so different machines that share a hostname stay separate, and a machine reported by both RMMs is counted once in evidence.