NinjaOne StrawberryHand the NinjaOne devices to a companion
A companion works the 2 operations your NinjaOne account exposes. It can update a device and create a support ticket, and every one of those waits on an approval card showing the device before it changes.
Open the device. Check it against something else. Write the change. Move to the next one. That is the NinjaOne afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a device until you approve it.
What it can do is exactly what NinjaOne exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can update a device and create a support ticket, and work across the devices and support tickets.
The NinjaOne API stops at NinjaOne. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which NinjaOne devices does a companion see?
In the tab.
NinjaOne exposes no read operation to a connected account, so a companion opens NinjaOne in the session you are already signed into and reads the screens you would.
The devices are what most of this inventory is about, alongside the support tickets. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of NinjaOne admin becomes a queue you review.
Can it change a device without asking?
All 2 write operations wait for you.
A companion can update a device and create a support ticket, and each one is staged on an approval card first: you see the device, the field and the new value before it lands in NinjaOne.
Nothing in NinjaOne is sent, changed or deleted on your behalf without that click, and a rejected card leaves the device exactly as it was. The gate is the same one on every surface, described at security.
- Update Device
- Create Support Ticket
Can the devices pass run every Monday?
Yes.
Saved as a routine, the NinjaOne devices pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the site work, the NinjaOne devices sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents