ConductorOne Docs

JumpCloud integration

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.


JumpCloud is a cloud directory that centralizes management of user identities and devices, enabling small and medium-sized enterprises to adopt zero-trust security models.


βœ… General availability. The JumpCloud integration is available to all ConductorOne users.


  • Sync user identities from JumpCloud to ConductorOne
  • Resources supported:
    • Groups
    • Apps
    • Roles

Set up the JumpCloud integration

A user with the Super Administrator role in ConductorOne must perform this task.

  1. In ConductorOne, open Administer and click Integrations > JumpCloud.

  2. If this is your first JumpCloud integration, the integration form opens automatically. Otherwise, click Add connector.

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

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

    A JumpCloud integration owner must have the following permissions:

    • Integration Administrator or Super Administrator role in ConductorOne
    • An Administrator identity in JumpCloud
  1. Click Create and add details.

Next steps

  • If you are the integration owner, proceed to Integrate your JumpCloud instance for instructions on integrating JumpCloud with ConductorOne.

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

Integrate your JumpCloud instance

A user with the Integration 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, open Administer and click Integrations > JumpCloud.

  2. In the list of connectors, locate and click on the name of the connector with the Not connected label.

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

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

  5. Click Save.

  6. 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 instance is now integrated with ConductorOne.

What’s next?

If JumpCloud is your company’s identity provider (meaning that it is used to SSO into other software), the integration 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 integrations with 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.