Get the Guide to Modern IGA

ConductorOne Docs

Set up a JumpCloud connector

ConductorOne provides identity governance for JumpCloud. Integrate your JumpCloud instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.


General availability. The JumpCloud connector is available to all ConductorOne users.


  • Sync user identities from JumpCloud to ConductorOne

  • Resources supported:

    • Groups
    • Apps
    • Roles
  • Provisioning supported:

    • Group membership

Add a new JumpCloud connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, open Admin and click Connectors > Add connector.

  2. Search for JumpCloud and click Add.

  3. Choose whether to add the new JumpCloud connector as a data source to an existing application (and select the app of your choice) or to create a new application.

  4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

    A JumpCloud connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • An Administrator identity in JumpCloud
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your JumpCloud connector for instructions on integrating JumpCloud with ConductorOne.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your JumpCloud connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and an Administrator identity in JumpCloud on the relevant JumpCloud org must perform this task.

Step 1: Retrieve a JumpCloud API key

  1. In JumpCloud, log in as an Administrator.

  2. Click your user avatar at the top right corner of the page and click My API Key.

  3. Copy the API key. We’ll use it in the next step.

Step 2: Add your JumpCloud credentials to ConductorOne

  1. In ConductorOne, navigate to the JumpCloud connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Admin > Connectors > JumpCloud (if there is more than one JumpCloud listed, click the one with your name listed as owner and the status Not connected).

  2. Find the Settings area of the page and click Edit.

  3. Paste the API key you looked up in Step 1 into the API key field.

  4. Click Save.

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

That’s it! Your JumpCloud connector is now pulling access data into ConductorOne.

What’s next?

If JumpCloud is your company’s identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the Create applications page for important information about how to set up connectors for the SCIMed apps.

Configure the JumpCloud integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between JumpCloud and ConductorOne.

See the ConductorOne JumpCloud integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Troubleshooting the JumpCloud integration

Why do I see multiple accounts for some JumpCloud users?

JumpCloud separates users and admin users, giving each a separate identity and login. Because of this, a user who is both a user and an admin user in JumpCloud will have two JumpCloud accounts in ConductorOne.

Why don’t I see profile attributes listed for a JumpCloud admin user?

An admin user in JumpCloud is intended only to manage the JumpCloud tenant, and not to be an identity that gains access to resources. Because of this design, admin users are not associated with the profile attributes, such as department or job title, that are associated with a non-admin user account.