Set up NinjaOne connector

Capabilities

Resource	Sync	Provision
Account
Role

Additional functionality: Supports automatic account provisioning and deprovisioning

Gather NinjaOne configuration information

Configuring the connector requires you to pass in information from NinjaOne. Gather these configuration details before you move on. Here’s the information you’ll need:

NinjaOne Base URL
NinjaOne Client ID
NinjaOne Client Secret
NinjaOne Scope

A user with the Admin role in NinjaOne must perform this task.

Create a NinjaOne application

Log into NinjaOne and navigate to Configuration > Apps > API > Client App IDs.

Click Add.

Select API Services (machine-to-machine) as the application platform.This creates an M2M app suitable for the Client Credentials Flow used by this connector.

Configure the application’s settings:

Name: Enter a descriptive name (e.g., “Baton NinjaOne Connector”)
Redirect URIs: Leave empty (not needed for M2M applications)
Scopes: Select the required scopes (see below)
Allowed Grant Types: Ensure “Client Credentials” is enabled

Give the application the relevant set of scopes:For Syncing (Read-Only Operations):

monitoring - Required to read user information and organizational structure
management - Required to read role definitions and user-role assignments

For Provisioning (Read-Write Operations):

monitoring - Required to read user information and organizational structure
management - Required to create/delete users and manage user information
control - Required to manage role assignments and user permissions

After saving, carefully copy and save the client ID and client secret.

Done. Next, move on to the connector configuration instructions.

Configure the NinjaOne connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of NinjaOne configuration information gathered by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for NinjaOne and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Enter the configuration information from the previous section.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your NinjaOne connector is now pulling access data into C1.

Follow these instructions to use the NinjaOne connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.

Step 1: Set up a new NinjaOne connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your NinjaOne connector deployment:

Secrets configuration

# baton-ninja-one-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-ninja-one-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # NinjaOne config
  BATON_NINJA_ONE_BASE_URL: <Base URL for your NinjaOne instance (e.g., https://app.ninjarmm.com)>
  BATON_NINJA_ONE_CLIENT_ID: <OAuth2 Client ID for NinjaOne API>
  BATON_NINJA_ONE_CLIENT_SECRET: <OAuth2 Client Secret for NinjaOne API>
  BATON_NINJA_ONE_SCOPE: <OAuth2 Scope for NinjaOne API>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-ninja-one.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-ninja-one
  labels:
    app: baton-ninja-one
spec:
  selector:
    matchLabels:
      app: baton-ninja-one
  template:
    metadata:
      labels:
        app: baton-ninja-one
        baton: true
        baton-app: ninja-one
    spec:
      containers:
      - name: baton-ninja-one
        image: ghcr.io/conductorone/baton-ninja-one:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-ninja-one
        envFrom:
        - secretRef:
            name: baton-ninja-one-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the ninja-one connector to. ninja-one data should be found on the Entitlements and Accounts tabs.

Done. Your NinjaOne connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up NinjaOne connector

Capabilities

Gather NinjaOne configuration information

Create a NinjaOne application

Configure the NinjaOne connector

Resources

Step 1: Set up a new NinjaOne connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather NinjaOne configuration information

​Create a NinjaOne application

​Configure the NinjaOne connector

​Resources

​Step 1: Set up a new NinjaOne connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather NinjaOne configuration information

Create a NinjaOne application

Configure the NinjaOne connector

Resources

Step 1: Set up a new NinjaOne connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector