Integrations

RMM integrations: NinjaOne, Datto RMM and N-central

Connect NinjaOne, Datto RMM or N-central to see which of each client's workstations don't have Enlist yet, import clients, and install Enlist through the RMM.

Connect your RMM and Enlist reads each client's Windows and Mac workstations from it, shows which ones already have Enlist (by serial number), and installs Enlist on the rest by running a script through the RMM. You never visit the devices. One RMM can be connected at a time, alongside your PSA.

What Enlist does in your RMM #

Reads, every day
Enlist reads the organizations (NinjaOne), sites (Datto RMM) or customers (N-central), and their Windows and Mac workstations. Servers, phones and network devices are left out. It reads again every day, and when you pick Read now.
Finds what's missing
A workstation has Enlist when an Enlist device has the same serial number. Datto RMM and N-central only give serial numbers device by device, so on a big RMM they fill in over the first hour.
Installs Enlist
When you push, Enlist makes one enrollment token for just the devices you picked, valid for a day, and asks the RMM to run your install script on each one with that token. The device enrolls into the client (and site) you mapped, and starts its onboarding like any other.
Never twice
A device that got Enlist in the meantime is skipped. If the RMM doesn't answer, Enlist tries again a few times. If the RMM answered with an error after it may have started the script, Enlist marks the push failed and says so, instead of running it a second time.

Enlist never changes anything else in your RMM: no devices, policies or organizations.

Connect NinjaOne #

  1. In NinjaOne, open Administration, then Apps, then API, and on Client app IDs choose Add.

  2. Set Application platform to API Services (machine-to-machine), name it Enlist, tick the scopes Monitoring and Management, and the grant type Client credentials. Save, then copy the client id and client secret.

  3. In Enlist, open Settings → RMM. Pick NinjaOne and the region you sign in at, paste the Client id and Client secret, pick Connect and approve with your passkey.

Connect Datto RMM #

  1. In Datto RMM, open Setup, then Global Settings, then Access Control, and turn on Enable API Access.

  2. Open Setup, then Users, edit the user Enlist will act as, and choose Generate API Keys. Copy the API Key and API Secret Key.

  3. In Enlist, open Settings → RMM. Pick Datto RMM and your platform (it's in the address you sign in at, such as merlot.centrastage.net), paste the keys, pick Connect and approve with your passkey.

Connect N-central #

  1. In N-central, add a user for Enlist under Administration → User Management, with a role that can see devices and add scheduled tasks. Turn off two-factor sign-in for that user (N-central requires it for API users).

  2. On the user's API Access tab, choose Generate JSON Web Token and copy it.

  3. In Enlist, open Settings → RMM. Pick N-able N-central, enter your server's address (such as ncentral.example.com), paste the token, pick Connect and approve with your passkey.

Add the install script #

Under Install script, open Windows script or Mac script and copy it. The script holds no secret: Enlist passes the token each time it runs it.

  • NinjaOne: add it under Administration → Library → Automation as a PowerShell script for Windows and a ShellScript for Mac, then pick Read the scripts in Enlist and choose them.

  • Datto RMM: add a component under Automation → Components, category Scripts, with a String variable named EnlistToken. Only components with that variable are listed in Enlist.

  • N-central: add it to Script/Software Repository (PowerShell for Windows, a Mac script for Macs) and type its id in Enlist.

Saving the scripts asks for your passkey, since they run as SYSTEM or root.

Map clients #

Under Clients, pick Map clients. Enlist suggests the organization with the same name; pick Use to accept it, or pick another. Choose a site if pushed devices should enroll into one. To bring clients over from the RMM, open Import unmapped organizations as clients, tick them and pick Import: a client with the same name is mapped instead of added twice.

Install Enlist on a client's workstations #

  1. Open the client from Clients. Under its devices, In NinjaOne (or Datto RMM, N-central) lists the workstations that don't have Enlist yet.

  2. Tick the devices, or pick Pick all without Enlist (up to 200 at a time), then Install Enlist and approve with your passkey. You need the Operate devices permission on the client.

  3. Each row shows Waiting to send, then Sent to the RMM. The device shows up in Enlist when the script has run on it. A failed row says why.

Change, pause or disconnect #

Pause stops reading and pushing. Pasting a new secret changes it; leave it blank to keep the current one. Moving to another RMM, address or account needs the secret again and clears the mapping and the scripts. Disconnect forgets everything Enlist read and cancels pushes not sent yet, after a passkey check. Devices that already have Enlist stay as they are. Every change shows in Activity.

Last updated 2026-11-15. Something wrong or missing? Email [email protected].