SeatReaper reads every approved Windows, Mac and Linux device in your NinjaOne organizations, with when NinjaOne last heard from it and who last signed in. It never changes devices, policies or scripts.
Create an API app
- Sign in to NinjaOne as a system administrator.
- Open Administration > Apps > API, then Client app IDs, and choose Add.
- Choose the application platform API Services (machine-to-machine). Give it a name such as SeatReaper.
- Under Scopes choose Monitoring only. Under Allowed grant types choose Client Credentials.
- Save, then copy the client ID and the client secret. The secret is shown once.
Note your region from the address you sign in at: app.ninjarmm.com, us2.ninjarmm.com, eu.ninjarmm.com, ca.ninjarmm.com or oc.ninjarmm.com.
Connect
An owner opens Settings > Integrations > NinjaOne, chooses the region, pastes the client ID and secret, and chooses Connect NinjaOne. SeatReaper signs in to check them, saves them encrypted, and runs the first sync. After that it syncs every day, and Sync now checks at any time.
How devices are linked to clients
- Each organization is linked to the client with the same name (ignoring capitals, punctuation and endings like Inc or LLC), or to the client an owner or tech picks under NinjaOne organizations. A picked link is kept on every sync.
- A device in an organization that is not linked still links to a client when exactly one client has a device with the same name in N-central, Datto RMM or Cove.
- Your other device tools use NinjaOne too: a CrowdStrike or Webroot device that is not linked follows the NinjaOne device with the same name.
Devices waiting for approval, and things NinjaOne monitors without an agent (VM hosts, network devices, cloud monitoring targets), are not read.
What SeatReaper does with it
- Dead devices: a device NinjaOne has not heard from for the device threshold (60 days unless you change it) is flagged, but only if every other tool it appears in also considers it dead. One item lists every tool still billing for it. See What SeatReaper flags.
- Offboarding: NinjaOne devices appear in the device list when you offboard someone, with the last signed-in user, and are confirmed once they leave NinjaOne.
- Prices: set your monthly cost per managed device in the price book.
Disconnect
An owner chooses Disconnect on the card. SeatReaper deletes the organizations and devices it synced. Delete the API app in NinjaOne to revoke access completely.
In compliance reports
On Growth and Pro, NinjaOne devices are the RMM column of the Device inventory and gaps report in the compliance evidence reports. A device any tool has seen recently counts as active, and active devices with no EDR or backup are listed first.