Overview
This guide explains the steps to integrate NinjaOne on the Josys App Catalog page.
Integration Specifications
| Target Plans | All |
|---|---|
| Admin Type for Integration | Technician |
| Integration Method | API Key/Token |
| Integration Keys | Client ID, Client Secret, Base URL |
| Supported Actions | Delete AccountVisualize AccountProvision Account |
| Account Visualization | ActivePendingInactive |
| Statuses Excluded from Unmanaged IDs | |
| Settings Available during Provisioning | Profile Settings |
| Contract Information | |
| Other Retrieved Items | ・User Type ・Organization |
| Visualized Items | ・Status ・Permissions ・MFA Enabled |
| Retrievable Permission Types | |
| Edit Permissions |
Prerequisites and Integration Types
The integration method varies depending on the type of NinjaOne environment you are using.
- For independent NinjaOne environments managed by yourself:
Use API Key integration.
Create a client application on your end and generate a Client ID and Client Secret. - For MSP environments provided by Josys:
Use OAuth integration.
Receive a dedicated technician account issued by the Josys EMS team, and use that account to integrate and authorize.
You do not need to create web apps, technicians, or configure permissions for multiple companies yourself.
The scope of data retrieved depends on the permissions and organizations configured for the issued account.
Integrating NinjaOne
NinjaOne Configuration
- Log in to the NinjaOne admin console.
- Click "Administration" > "Apps" > "API".
- Click "Add Client App" to open the creation screen.
- Select "Web (PHP, Java, .Net Core, etc.)" for the Application Platform.
- Configure the following settings:
- Name: Any name (e.g., Josys Integration)
-
Redirect URI:
- JP Environment:
https://app.josys.it/admin/integrations/callback/ninjaone - US Environment:
https://app.us.josys.it/admin/integrations/callback/ninjaone
- JP Environment:
- Scopes: Check all three scopes ("Monitoring", "Management", and "Control").
- Allowed Grant Types: Check "Authorization Code" and "Refresh Token".
- Click "Add" in the bottom right to generate the Client ID and Client Secret. Copy these values. *The secret is only displayed once upon creation, so make sure to save it in a secure location.
💡 The secret is only displayed when it is created. It cannot be retrieved again after closing the screen, so be sure to save it in a secure place, such as a password manager.
Josys Configuration
- From the Josys menu, click "Integrations" > "App Catalog".
- Search for and select "NinjaOne".
- On the setup page on the right side of the screen, select the integration method from the dropdown.
- Enter the copied Client ID, Client Secret, and your environment's Base URL.
- Click "Next" in the bottom right.
- For OAuth integration, you will be redirected to the NinjaOne login and authorization screen. Sign in using the dedicated technician account provided by the Josys EMS team and authorize the integration.
- Once the integration process is complete and you can verify the connection and synchronization status, the setup is complete. If you wish to continue integrating Devices, please refer to the Devices External Data Sources setup page.
Important Notes & FAQ
Q: The integrated NinjaOne technician account is not retrieved or displayed on Josys. Also, I cannot assign devices to it.
Due to NinjaOne's permission design specifications, technician accounts cannot view other technician accounts. Therefore, the technician account used for this integration itself will not be retrieved or displayed in Josys, and you cannot assign devices to that account (including manual operations). Please be aware of this limitation in advance.Q: The actual MFA settings status may differ from the MFA enabled status displayed in Josys. What should I check?
The MFA enabled status retrieved from NinjaOne may sometimes differ from the actual status. Please do not rely solely on the "MFA Enabled" display in Josys to determine if MFA is actually configured. If necessary, verify the correct configuration status in the NinjaOne admin console.