> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/ninjaone-integration-setup.md).

# NinjaOne Integration Setup

### Getting Started

Use this guide to connect NinjaOne to your BalkanID tenant. BalkanID reads your NinjaOne technicians, end users, roles, organizations, locations, devices, groups, policies, document templates, credentials, and software licenses, and the permissions that connect them, so you can review who can reach which device or organization and how.

You will need an API client from your NinjaOne instance and access to the Integrations section in BalkanID.

#### Requirements:

Before you begin, collect the following values from NinjaOne:

* **Client ID**
* **Client Secret**
* **Region**

### Configure NinjaOne within your BalkanID tenant

1. To create the **Client ID** and **Client Secret**, sign in to your NinjaOne instance as an administrator.
2. Navigate to **Configuration** > **Apps** > **API** > **Client App IDs**, then select **Add**.
3. Create an **API Services (machine-to-machine)** application.
4. Set the application's scope to **Monitoring** (see [Integration Scopes](#integration-scopes) below). Do not grant the Management or Control scopes.
5. Copy the generated **Client ID** and **Client Secret**. NinjaOne shows the secret only once.
6. Note your **Region** — the subdomain in your NinjaOne sign-in URL (`https://<region>.ninjarmm.com`), one of `app`, `us2`, `eu`, `ca`, or `oc`. Credentials are bound to the region they were created in.
7. In BalkanID, go to **Configure** > **Integrations** and select **Add integration**, then search for **NinjaOne**, select the application, and click **Next**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fgit-blob-8458eac2bc6df15ed24f4cee3b094ae4cf5c5ec2%2Fninjaone-connect-application.png?alt=media" alt="The Connect a new application step with NinjaOne found in the application search"><figcaption><p>Connect a new application</p></figcaption></figure></div>

8. Under **Select Extraction Type**, keep **Direct Configuration** selected and paste your **Client ID**, **Client Secret**, and **Region** into the corresponding fields, then click **Next**. The Required API Scopes panel above confirms `monitoring` is the only scope BalkanID asks for.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fgit-blob-baf05b87cef523ddec47b2ed92a66848e9cceb62%2Fninjaone-direct-configuration.png?alt=media" alt="The Required API Scopes panel and the Direct Configuration step showing the Client ID, Client Secret, and Region fields"><figcaption><p>Direct Configuration</p></figcaption></figure></div>

9. Fill **Optional Configuration**, if required.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FZbipc8nl8LTFl5YsVIaj%2Foptional-configuration.png?alt=media&amp;token=2eb26e28-a526-4592-87c1-84e90b6fb30a" alt="The Optional Configuration step of the integration wizard"><figcaption><p>Optional Configuration</p></figcaption></figure></div>

10. Once you have filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status column will read **Connected** and the integration Message will read **Data available**.

### What BalkanID extracts

| Type                              | Description                                                                                                                                                                                     |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Technicians**                   | Administrators and support staff on your NinjaOne instance, including their role assignments, MFA status, and organization access granted through System Administrator or "Permit All Clients." |
| **End users**                     | Portal end users at your NinjaOne organizations, including their role assignments and device access.                                                                                            |
| **Technician and end-user roles** | The roles in your NinjaOne instance and who holds each one.                                                                                                                                     |
| **Organizations and locations**   | The organizations (clients) and locations configured in your NinjaOne instance.                                                                                                                 |
| **Devices**                       | Managed endpoints, including which technicians and end users own or can access each one.                                                                                                        |
| **Groups and policies**           | Saved device searches and RMM policies, and the devices each one applies to.                                                                                                                    |
| **Document templates**            | Templates and which technician roles can access them.                                                                                                                                           |
| **Credentials**                   | Credentials tracked in NinjaOne's asset inventory (SNMP, SSH, encryption keys, and similar), and the identities and devices they relate to. Secret values are never extracted.                  |
| **Software licenses**             | Per-user software license assignments.                                                                                                                                                          |

BalkanID does not extract employee/HR records or an AI agent inventory from NinjaOne — its API exposes neither.

### Integration Scopes

| Read Only Scopes                                                                                                                                                   | Lifecycle Management Scopes |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------- |
| **Monitoring (Read)** — technicians, end users, roles, organizations, locations, devices, groups, policies, document templates, credentials, and software licenses | N/A                         |

### Requirements and limitations

* Only the **Monitoring** scope is required. Do not grant the Management or Control scopes to the API client used for this integration — BalkanID never needs write or remote-access permissions.
* Technician access granted through a role's organization permissions cannot be read back from the NinjaOne API. BalkanID reports organization access only for technicians who are System Administrators or have "Permit All Clients" enabled; access granted purely through a role's organization scoping will not appear in BalkanID.
* NinjaOne credentials are discovered through their relationships to other assets in NinjaOne. A credential with no relationships and no device binding is not visible to BalkanID.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/ninjaone-integration-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.