Integrations
RMM Integration - NinjaOne
Overview
Remote Monitoring and Management (RMM) allows Managed Service Providers (MSPs) to remotely deploy, monitor, and manage software across customer devices.
The Evo Security RMM integration with NinjaOne allows administrators to deploy, upgrade, and uninstall the Evo Agent directly from the Evo Portal while leveraging NinjaOne to execute deployments across managed endpoints.
Prerequisites
Before configuring the integration, ensure you have:
- Administrator access to both the Evo Portal and NinjaOne.
- An existing NinjaOne RMM environment.
- A Client Application created within NinjaOne.
- Appropriate permissions within Evo Security to manage RMM integrations and deployments.
Creating a NinjaOne Client Application
To allow Evo Security to communicate with NinjaOne, you'll first need to create an API Client Application.
Within the NinjaOne Portal:
Administration → Apps → API → Client App IDs
- Select Add Client App
- Choose Single Page Application
- Enter a name
- Set the Redirect URI to: http://localhost ( this is temporary )
- Select the following scopes:
- Monitoring
- Management
- Control
- Under Allowed Grant Types, select:
- Authorization Code
- Save the application.
After saving:
- Edit the application.
- Enable:
- Refresh Token
- Update your changes.
Note: Record the Client ID, as it will be required when configuring Evo.
Configuring the RMM Integration
In the Evo Portal navigate to:
Evo Admin → Integrations → RMM
Select Configure, then click New.
Complete the configuration:
Setting | Value |
Provider | NinjaOne RMM |
Base URI | |
Client ID | Your NinjaOne Client ID |
Note: The Base URI should be your Ninja Instance URL based on your location:
USA 1: app.ninjarmm.com USA 2: us2.ninjarmm.com Europe: eu.ninjarmm.com Oceania : oc.ninjarmm.com Canada: ca.ninjarmm.com
Save the configuration.
After saving, Evo will generate a Callback URI.
Adding the Callback URI
Return to your NinjaOne Client Application.
Navigate to:
Administration → Apps → API → Client App IDs
Edit your application.
Under Redirect URIs:
- Remove the temporary localhost URI.
- Add the Callback URI generated by Evo.
- Save the application.
Authorizing the Integration
Return to the Evo configuration page.
Select Authorize.
You'll be redirected to NinjaOne to approve the requested permissions.
After approving access, you'll automatically return to Evo where access and refresh tokens will be created.
Token Notes
- Access tokens are automatically refreshed when needed.
- Refresh tokens are renewed automatically.
- By default, NinjaOne refresh tokens expire after 30 days.
- Contact your NinjaOne Account Manager if you'd like to enable Sliding Refresh Tokens, which prevent manual reauthorization.
Creating a Mapping
Mappings associate an Evo tenant with a NinjaOne organization.
Navigate to:
Integrations → RMM → Mappings
Select New.
Configure:
- Tenant
- Directory (optional)
- RMM Integration
- Scope (NinjaOne Organization)
Save the mapping.
Mappings are used during device discovery and deployment.
Note: Mappings associate an organization with its Evo tenant and directory (when configured). This information is used during deployments to automatically identify the correct tenant and directory, allowing Evo to generate and configure deployment tokens whenever possible.
Creating Deployment Scripts
Deployment scripts are required for installing, upgrading, or uninstalling the Evo Agent.
Within NinjaOne:
Administration → Library → Automation
Create a new script.
Recommended settings:
Setting | Value |
Language | PowerShell (Windows) or ShellScript (macOS) |
Run As | System |
Architecture | x64 |
Operating System | Windows or macOS |
Upload or paste the appropriate Evo installation script and save.
Note: Our Deployment Scripts can be found HERE under Assets
Deploying the Evo Agent
Navigate to:
Desired Tenant → Endpoints → RMM Deployments
Select New.
Choose:
- Tenant
- Provider
- Scope
- Deployment Token
- Target devices
Select the installation script for the appropriate operating system.
If upgrading existing agents, choose whether to:
- Use existing settings
- Apply new deployment settings
Save the deployment.
Deployment status can be monitored from the Deployments page.
If a deployment has not started, it can be cancelled.
Note: You can deploy the agent from the global context, but it requires the selection of a tenant.
Device Discovery
Device Discovery associates NinjaOne-managed devices with existing Evo Computers.
Discovery runs automatically every 4 hours after a mapping has been created.
Manual discovery can also be performed.
To manually start discovery:
- Navigate to Integrations → RMM
- Edit the integration
- Under Discovery History, select the Search icon
Note: Manual discovery is limited to 3 executions per hour.
Computers
After the Evo Agent is successfully deployed:
- Devices appear under Endpoints → Computers
- Successfully discovered devices are marked as RMM Managed
Note: When deleting an RMM-managed computer from Evo, the system first attempts to uninstall the Evo Agent before removing the computer record.
Deployment History Retention
A deployment history retention policy controls how long deployment records remain visible.
Default: 90 days
Supported values:
- Minimum: 30 days
- Maximum: 365 days
Deployment history is automatically cleaned up each day.
Permissions
The following permissions are available for RMM management:
Permission | Description |
Manage RMM Integrations | Allows users to configure and manage RMM integrations. |
Manage RMM Deployments | Allows users to create and manage RMM deployments. |