NinjaOne is a remote monitoring and management (RMM) platform that you can connect to Strategy Overview as your PSA integration. This guide covers the NinjaOne-specific steps for creating API credentials and connecting. For the common setup steps that follow (mapping companies, importing configurations, and importing contacts), see Configuring Your PSA Integration.
One PSA at a time. You can only have one PSA integration connected. If NinjaOne is your primary system of record, connect it as your PSA. If you already run a different PSA (ConnectWise, Autotask, Halo, and so on), you can connect NinjaOne as a data integration instead, so it runs alongside your existing PSA.
Note: NinjaOne is an RMM, so it brings in your companies, devices, and contacts. It does not carry the documentation records (Flexible Assets, domains, SSL certificates) you would get from IT Glue or Hudu, and it does not sync tickets. Use a documentation platform alongside it if you need 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.
Once connected, follow the common steps in Configuring Your PSA Integration to enable and map your Companies, Configurations, and Contacts.
Next step: Configuring Your PSA Integration