NinjaOne RMM Integration Setup Guide

NinjaOne connects to Scopable with read-only API credentials. You create a small API app in NinjaOne, paste its Client ID and Secret into Scopable, pick your region, and map each NinjaOne organization to the matching Scopable client.

What this does today: the current release establishes the connection and lets you map organizations to clients. Pulling devices, patch status, and antivirus/EDR posture into Scopable (and into compliance evidence) is on the roadmap and will build on the organization mapping you set up here. Connecting now gets your organizations linked so that data lands in the right place when it ships.

NinjaOne is an RMM, so it runs alongside your PSA, so there's no conflict with ConnectWise or another PSA.

Step 1: Create a read-only API app in NinjaOne

In the NinjaOne portal:

1. Go to Administration → Apps → API.
2. Create a new Client App using the client-credentials (machine-to-machine) flow.
3. Request the read-only monitoring scope. Scopable only ever reads from NinjaOne; it does not request management or remote-control access.
4. Save the app and copy the Client ID and Client Secret.

The exact screens and field names in NinjaOne can change. NinjaOne's own walkthrough for creating an API app is the authoritative reference: see NinjaOne's documentation, "How to set up API OAuth token." The key choices are client-credentials grant and the monitoring (read-only) scope.

Know your region

NinjaOne runs several regional instances. You'll select yours in Scopable, and it must match the host you log in to:

Region	NinjaOne host
United States	app.ninjarmm.com
United States 2	us2.ninjarmm.com
Europe	eu.ninjarmm.com
Canada	ca.ninjarmm.com
Oceania	oc.ninjarmm.com

Step 2: Open the NinjaOne RMM integration in Scopable

1. Log in to Scopable as an Admin.
2. Click Integrations in the left-side navigation under Administration.
3. Open the NinjaOne RMM tab.

The NinjaOne RMM card shows Status: Not connected with Organizations and Read-only badges.

Don't see a NinjaOne RMM tab? This integration is rolled out gradually. If you see "The NinjaOne RMM integration is currently not available for your account," or the tab is missing, it isn't enabled for your account yet. Contact your administrator or Scopable for access.

Step 3: Connect and test

1. Click Connect to open the Connect NinjaOne dialog.
2. Fill in:
   • Region: pick the region matching your NinjaOne login (see the table above). Defaults to United States.
   • Client ID: from the API app you created in Step 1.
   • Client Secret: from the same app (stored encrypted in Scopable's secure vault; never shown again).
3. Click Test connection. On success, Scopable reports how many organizations it found. The test doesn't save anything yet.
4. Click Connect to save. (This button stays disabled until a test passes.) You'll see a confirmation that the credentials were saved and it's time to map organizations.

Step 4: Map organizations to clients

After connecting, the page shows the Organization mapping card: "Link each NinjaOne organization to the matching Scopable client."

• The table lists each NinjaOne organization beside a Scopable client dropdown.
• Choose the matching client to map it. Choose Not mapped to unmap.
• Use Refresh to re-pull organizations from NinjaOne if you add new ones.

Each NinjaOne organization maps to one Scopable client. Reassigning an organization automatically clears its previous mapping.

Troubleshooting

The NinjaOne RMM tab isn't there

The integration is enabled gradually. If the tab is missing, your account hasn't been enabled. Contact your administrator or Scopable.

"NinjaOne rejected those credentials" on Test connection

The Client ID or Secret is wrong, or the API app wasn't created with the client-credentials flow and the monitoring scope. Re-copy both values (no trailing spaces) and test again.

Test fails even though the credentials look right

Check your Region. The region selects which NinjaOne host Scopable authenticates against. A EU/US2/CA/OC tenant connected as "United States" will fail. Pick the region matching your login host.

"No NinjaOne organizations yet"

There are no organizations in your NinjaOne account, or none were returned. Confirm your organizations in NinjaOne, then click Refresh.

Mapping fails

Each organization maps to one client. If a mapping fails, the target client may already be mapped to another organization. Reassigning normally clears the old link automatically; if it doesn't, unmap the conflicting one first, then try again.

Still stuck?

Email us at [email protected] with a screenshot of the error and we'll help you get connected.

Frequently Asked Questions

Does connecting NinjaOne let Scopable change anything in my RMM?

No. Scopable requests only the read-only monitoring scope. It reads organizations (and, on the roadmap, device and posture data). No management or remote-control access is requested.

Does it sync my devices, patch status, or antivirus posture today?

Not yet. The current release connects credentials and maps organizations to clients. Device sync and patch/AV/EDR posture (including into compliance evidence) are on the roadmap and will build on this mapping.

Will this conflict with my PSA?

No. NinjaOne is an RMM and runs alongside your PSA, with no mutual-exclusivity check.

Where is my Client Secret stored?

Encrypted in Scopable's secure vault. It's never shown in the interface after you enter it, and disconnecting removes it.

What does mapping organizations to clients actually do?

It links each NinjaOne organization to the matching Scopable client so RMM data resolves to the right client. One organization maps to one client; reassigning clears the previous link.