NinjaOne: devices, patch and antivirus posture, and active alerts

NinjaOne (the RMM formerly sold as NinjaRMM) holds your managed endpoints and the network gear alongside them. This connector reads four things out of it: the device inventory, patch posture, antivirus status, and the alerts currently firing — and hangs each one off the matching Current company so it feeds your executive and CIO business reviews and the company alert band. Current reads NinjaOne and can never change anything in it.

1. 1
   1 · Open Administration ▸ Apps ▸ API

   Sign in to NinjaOne as an administrator and go to Administration → Apps → API. This is where NinjaOne's API client applications are created.
2. 2
   2 · Add an API Services (machine-to-machine) app

   Press Add and choose API Services (machine-to-machine). That application type authenticates as itself with a client id and secret, so nobody has to stay signed in for the sync to run.
3. 3
   3 · Grant the Monitoring scope

   Tick Monitoring and nothing else. Monitoring is the read scope that covers organizations, devices, queries, and alerts. Leaving the management and control scopes off means the credential itself has no way to change anything in NinjaOne.
4. 4
   4 · Copy the Client ID and Client Secret

   NinjaOne shows the secret once, at creation. Copy both values before you close the dialog — a lost secret means creating a new application.

1. 1
   Open the NinjaOne card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link) and find NinjaOne in the Reporting integrations section.
2. 2
   Pick your region

   NinjaOne runs separate instances and your credentials only work against yours. Match the address you sign in at: North America (app.ninjarmm.com), US2 (us2.ninjarmm.com), Europe (eu.ninjarmm.com), Canada (ca.ninjarmm.com), or Oceania (oc.ninjarmm.com).
3. 3
   Paste the Client ID and Client Secret, then press Test connection

   Current trades the pair for a token against the region you picked and reads a single organization back to prove the scope is right, before it stores anything. If NinjaOne refuses, the card shows NinjaOne's own reason rather than a generic failure. On success the secret is stored server-side only — the browser never sees it again.

NinjaOne syncs every 6 hours on a schedule, plus whenever you press Sync now on the card. Each run walks your organizations and devices, pulls the patch and antivirus reports, and replaces the active alert set.

Every request Current makes to NinjaOne passes through a read-only guard that permits only the specific read endpoints this article describes, plus the token exchange itself. Script execution, device commands, software deployment, policy edits, and organization management are absent from the list and unreachable, so a code bug cannot reach them either. NinjaOne stays the source of truth; Current only reads.

In NinjaOne each end-customer is an organization. Current lists all of them and links each to a Current company by normalized name — lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped — and only when exactly one company matches. Two companies that both fit stay unmapped for you to decide.

1. 1
   Let the auto-matcher run first

   Every sync links each organization to the one Current company whose normalized name matches. Most organizations map themselves; only the ambiguous ones need a hand.
2. 2
   Open the mapping panel

   Integrations → NinjaOne → Manage → Customer mapping. It opens on the Unmapped tab, which lists every organization the matcher could not place.
3. 3
   Map an organization to its company

   On an unmapped row press Map, type a few letters of the Current company, and pick it. That organization's devices and alerts attach to the company right away, rather than waiting for the next 6-hour sync.
4. 4
   Ignore internal or test organizations

   For an organization that should never map to a customer — your own internal fleet, a lab, a demo tenant — press Ignore. It moves to the Ignored tab and stops counting against the card's unmapped badge.
5. 5
   Fix a wrong match later

   The Mapped tab lists every linked organization; Unmap corrects a bad auto-match, and the Ignored tab's Un-ignore brings a dismissed one back. A mapping you set by hand is never overwritten by a later auto-match, and neither is a manual unlink.

• ＋The company's posture panel: device counts by class, patch compliance, and antivirus health for the mapped organization.
• ＋The Fleet & Network chapter of a Strategic Business Review, alongside your other RMM and network feeds.
• ＋Dashboard device metrics — endpoint counts and device-compliance percentages can read from NinjaOne once it is connected and mapped.
• ＋The company alert band: an active-alerts entry that turns critical on the first critical NinjaOne alert, and warns once critical and major alerts together reach three. It clears itself when the conditions reset in NinjaOne.