NinjaOne is a unified IT management platform that now includes both RMM and PSA capabilities. You can connect it to Strategy Overview two ways: as your PSA integration, or as a data integration that runs alongside a different PSA. Setup on the NinjaOne side is the same either way.
Choose the connection that fits how you use NinjaOne:
As your PSA: if NinjaOne is your primary system of record. You can only have one PSA connected at a time.
As a data integration: if you already run another PSA (ConnectWise, Autotask, Halo, and so on). NinjaOne runs alongside it, like IT Glue or Hudu.
Strategy Overview brings in your NinjaOne companies, devices, and contacts. It does not pull tickets or documentation records (Flexible Assets, domains, SSL certificates); use IT Glue or Hudu for those.
If your NinjaOne environment requires IP whitelisting, add the Strategy Overview IPs before connecting. See the IP Allow List article.
Before you start
A few things to have ready before you create credentials:
You need a system administrator account in NinjaOne. Only administrators can create API client apps.
Know the domain you sign in to NinjaOne with, including
https://(for example,https://app.ninjarmm.com/for North America orhttps://ca.ninjarmm.com/for Canada). You will enter this as the Server Domain Name when you connect.
Have a secure place ready to store the Client Secret. NinjaOne shows it only once, right after you create the app.
Create API credentials in NinjaOne
You will create an API client app that uses the client credentials (machine-to-machine) flow. This produces a Client ID and Client Secret to enter in Strategy Overview.
In the left menu, open Administration.
Go to Apps > API and select the Client app IDs tab.
Click Add client app.
In Application platform, choose API Services (machine-to-machine). This is the correct type for a server-to-server connection like Strategy Overview.
Fill in the application details:
Name: A label for the app, for example
Strategy Overview Integration.Redirect URIs: Required by the form even for machine-to-machine apps. If you do not have a callback URL, enter
https://localhost. The form will not save while this field is empty.
Under Scopes, select the access the integration needs:
Monitoring: read access to monitoring data and your organization structure.
Management: access to devices and organizations.
Leave Control unchecked unless remote control is required.
Under Allowed grant types, check Client credentials. This is the unattended, server-to-server flow Strategy Overview uses.
Click Add. NinjaOne creates the app and displays the Client ID and Client Secret.
Copy both immediately and store them securely.
Important: The Client Secret is shown only once. If you lose it, you cannot retrieve it. You will need to generate a new secret (or a new client app) and update the integration with the new value.
Add the integration in Strategy Overview
Go to Settings > Integrations > Add Integration and select NinjaOne.
On the Connection tab, enter:
Server Domain Name: the full URL you sign in to NinjaOne with, including
https://(for example,https://ca.ninjarmm.com/).Client ID: from the app you created.
Client Secret: from the app you created.
Save the connection.
After you connect
What comes next depends on how you connected NinjaOne:
As your PSA: follow Configuring Your PSA Integration for the shared steps: mapping company types and statuses, importing companies, and importing configurations and contacts.
As a data integration: on the Companies and Configurations tabs, map your NinjaOne companies to your existing Strategy Overview companies and import the device types you need, the same way as other data integrations.