NinjaOne
NinjaOne's RMM — devices, patches, and alerts on tap.
NinjaOne manages your endpoints across every organization you look after. It isn't on the board yet — the connection is being built in the open, and this page is the plan, not a shipped feature. Once it's connected, a session will be able to query device health, patch posture, alert history and software inventory without you opening a console tab per org.
The story
What changes once it’s connected.
NinjaOne knows the state of every endpoint you manage. The friction is that getting at it means picking an organization first, and the questions that matter rarely stop at one. Which devices haven't checked in for a week — across all of them. Pending OS patches, grouped by organization, so you can see who's actually behind. What triggered last night's alerts. Once NinjaOne is on the board, those will be asked once and answered across the whole book of clients.
It's in the works, not connected, so treat everything above as what's coming rather than what's running. The connection will be an OAuth client-credentials app you register in NinjaOne yourself, scoped for reads and pointed at your instance region, which keeps the credential yours and revocable in your own console. When it ships, this page gains what every live integration here already has: the complete skill list, and a plain statement of what the connection can't do.
What you’ll be able to ask
Here’s what’s coming.
Connecting
Wire it in, in an afternoon.
How connecting will work
- 01You'll create an API app in NinjaOne (Administration → Apps → API) using client credentials.
- 02Grant it the monitoring (read) scope, and note which instance region your tenant sits in.
- 03Region, client id, and client secret get entered here.
Patch your stack in.
Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.