AI Center: Connect Robin to JumpCloud

Connect JumpCloud to Atera so Robin can resolve JumpCloud identity requests for your end users, such as password resets, MFA resets, and locked accounts. Technicians can also manage JumpCloud users and groups from AI Copilot. You connect JumpCloud, an identity provider (IdP), with an API key, your Organization ID, and your Console URL, and you can sync your JumpCloud users into Atera.

Each customer has its own JumpCloud connection. Robin and AI Copilot always use the connection of the customer the ticket belongs to.

Your account has one JumpCloud connection, set up at the account level.

What Robin and AI Copilot can do in JumpCloud

When JumpCloud is connected, Robin and AI Copilot can act on JumpCloud users and user groups. Robin handles end-user requests. AI Copilot handles account and group changes for technicians.

Action	Available to	What it does
Check User Exists	Robin	Checks whether a JumpCloud user with the end user's email address exists
Get User Details	Robin	Gets the user's name, email address, secondary email, mobile phone, and other profile fields
Get Full User Details	Robin	Gets the same details plus the user's login name, status, created and activated dates, last password change, and user groups
Check User Group Membership	Robin	Checks whether the user belongs to a user group
Check Group Exists	Robin	Checks whether a user group exists
Reset User Password	Robin	Sets a temporary password that the user must change at their next sign-in
Reset User MFA	Robin	Resets the user's TOTP MFA
Unlock User	Robin	Unlocks an account that's locked after too many failed sign-in attempts
Update User	Robin	Updates fields on the user's profile, such as job title
Create User	AI Copilot	Creates a JumpCloud user, with a temporary password if none is given. It doesn't create a duplicate when the email address already exists
Enable User	AI Copilot	Activates the user's account
Disable User	AI Copilot	Suspends the user, which blocks their access to all JumpCloud resources
Reset User Password	AI Copilot	Sets a temporary password that the user must change at their next sign-in
Create Group	AI Copilot	Creates a user group
Add User to Group	AI Copilot	Adds the user to a user group
Remove User from Group	AI Copilot	Removes the user from a user group

Reset User Password is listed twice because Robin and AI Copilot each have their own version of it.

Password reset: Robin sets a temporary password in JumpCloud and marks it expired, so the user must change it at their next sign-in. This works only when Allow password change after expiration is on in JumpCloud. See Before you begin.
MFA reset: Robin resets the user's TOTP MFA in JumpCloud. The user has 7 days to set it up again. If they don't, JumpCloud locks them out of the User Portal.
Approvals: Robin runs Low-risk actions without asking. Before it runs a High-risk or Critical-risk action, the end user must approve that specific action in the conversation. The end user's original request doesn't count as approval. If an active playbook step calls for the action, Robin runs it without asking the end user.
Matching users: Robin finds a JumpCloud user by email address. The end user's email address in Atera must match their email address in JumpCloud.
AI Copilot actions in Robin: Robin doesn't run the AI Copilot actions on its own. If an end user asks for one, Robin either requests a technician's approval on the ticket or hands the ticket to a technician. To let Robin run one in a specific scenario, such as adding a new hire to a group after their manager approves, add the action to a playbook step.

The JumpCloud integration covers users and user groups only. It doesn't manage JumpCloud devices, device groups, policies, or SSO applications, and it doesn't write Atera changes back to JumpCloud.

Before you begin

To access AI Center, you need full admin permissions or a role with the AI center permission on its System tab. See Roles and permissions.
You need a JumpCloud administrator account with API access enabled. The API key Atera uses comes from this administrator. API access is off by default, and only an admin with the Administrator with Billing role can turn it on: in JumpCloud, go to Settings > Administrators, select details for the admin, and select Enable API access. See JumpCloud's Manage Admin Accounts.
For Robin's password resets to work, turn on Allow password change after expiration in JumpCloud (Settings > Security > Password Settings). Robin's reset sets a temporary password that's already expired, and JumpCloud blocks access to all resources for users with an expired password unless this setting is on. See JumpCloud's Manage Your Password Expiration Strategy.
To open AI Center, your account needs a Robin or AI Copilot license. Robin's JumpCloud actions need Robin, and the AI Copilot actions need AI Copilot.

Get your API key and Organization ID from JumpCloud

Atera connects to JumpCloud with an API key and an Organization ID, both from the JumpCloud Admin Portal. Copy them before you start the setup in Atera.

Copy your JumpCloud API key

Sign in to the JumpCloud Admin Portal as an administrator with API access enabled. If your organization's data is stored in the EU or India, use your region's login URL. See JumpCloud Data Centers: Login URLs and Service Endpoints.
At the bottom left of the page, click your admin name.
Select My API Key.
JumpCloud shows an API key only once, when it's created, so you can't copy an existing key from the API Key window. If you saved the key when you created it, use that one. Otherwise, select Generate New API Key, choose how long the key stays valid (for example, Expires in 90 days), and copy the new key right away. Generating a new key revokes the current one.

Warning: Generating a new API key revokes the current key right away. Anything that uses the old key stops working, including an existing Atera connection, until you enter the new key in Atera.

When you generate a key, you choose when it expires: 30, 60, or 90 days, a custom period, or no expiration. When the key expires, Robin can't act in JumpCloud until you enter a new key in Atera. For more about JumpCloud API keys, see JumpCloud's JumpCloud APIs article.

Copy your JumpCloud Organization ID

In the JumpCloud Admin Portal, go to Settings > Organization Profile.
Under General, find Organization ID.
Select the copy icon next to Organization ID. To see the full ID first, select the eye icon.

The Organization ID is now copied. Keep it and the API key ready for the setup in Atera.

Important: If your API key belongs to a multi-tenant (MSP) JumpCloud administrator, the connection doesn't work without the Organization ID. Enter it for every JumpCloud connection so Atera connects to the right JumpCloud organization.

MSPs: If you manage customers in JumpCloud's Multi-Tenant Portal, each customer is a separate JumpCloud organization with its own Organization ID. On the Organizations tab, select the customer's organization to see or copy its Organization ID. See JumpCloud's Manage Organizations in the MTP.

Connect JumpCloud in Atera

Connect JumpCloud separately for each customer that uses it. You need the API key and Organization ID you copied from JumpCloud.

In Atera, go to AI Center > Integrations > Product integrations.
In Manage integrations for, at the top of the page, select the customer.
Open the Discover tab.
Under Identity providers, select JumpCloud.
Enter the connection details:
- API key: Paste the API key you copied from JumpCloud.
- Organization ID: Paste the Organization ID you copied from JumpCloud.
- Console URL: Enter the console address for the region where your JumpCloud organization's data is stored: console.jumpcloud.com (US), console.eu.jumpcloud.com (EU), or console.in.jumpcloud.com (India). If you leave it blank, Atera uses the US console.
Leave Synchronize users on to import the customer's JumpCloud users into Atera as contacts, or turn it off. It's on by default.
Select Connect.

Atera checks the details with JumpCloud. When the connection succeeds, JumpCloud connected appears, and the JumpCloud card shows Active. If Synchronize users is on, Atera starts importing the customer's JumpCloud users as contacts right away.

Connect JumpCloud once for your account. You need the API key and Organization ID you copied from JumpCloud.

In Atera, go to AI Center > Integrations > Product integrations.
Open the Discover tab.
Under Identity providers, select JumpCloud.
Enter the connection details:
- API key: Paste the API key you copied from JumpCloud.
- Organization ID: Paste the Organization ID you copied from JumpCloud.
- Console URL: Enter the console address for the region where your JumpCloud organization's data is stored: console.jumpcloud.com (US), console.eu.jumpcloud.com (EU), or console.in.jumpcloud.com (India). If you leave it blank, Atera uses the US console.
Leave Synchronize users on to import your JumpCloud users into Atera as users, or turn it off. It's on by default.
Select Connect.

How JumpCloud user sync works

When Synchronize users is on, Atera imports the customer's JumpCloud users as contacts when you connect, and then updates them every 12 hours. Sync creates and updates contacts that come from JumpCloud. It doesn't change contacts you created manually or contacts synced from another identity provider.

When Synchronize users is on, Atera imports your JumpCloud users as users in Atera when you connect, and then updates them every 12 hours. Sync creates and updates users that come from JumpCloud. It doesn't change users you created manually or users synced from another identity provider.

Sync goes one way, from JumpCloud to Atera. Changes you make in Atera aren't written back to JumpCloud.
To sync now instead of waiting for the next 12-hour cycle, hover over the JumpCloud card, select the menu (three dots), and then select Sync contacts. A message appears: Syncing contacts… This may take a couple of minutes.

Manage or disconnect the JumpCloud connection

Update the JumpCloud connection when your API key changes, or disconnect it to stop Robin and AI Copilot from using JumpCloud.

For MSPs, select the customer in Manage integrations for first. Each customer's connection is managed separately.

Update the JumpCloud connection

In Atera, go to AI Center > Integrations > Product integrations.
Select the JumpCloud card.
Change the details you need:
- API key: Paste a new key to replace the stored one. Leave it blank to keep the current key. Atera never shows the stored key.
- Organization ID, Console URL, or Synchronize users: Change as needed.
Select Update.

Atera checks the details with JumpCloud. When the update succeeds, JumpCloud connected appears.

Disconnect JumpCloud

In Atera, go to AI Center > Integrations > Product integrations.
Hover over the JumpCloud card and select the menu (three dots).
Select Disconnect.
In the Disconnect JumpCloud connection window, select Disconnect.

JumpCloud disconnected appears, and the JumpCloud card no longer shows Active. Robin and AI Copilot stop using JumpCloud until you reconnect it. To reconnect, select the JumpCloud card and enter the connection details again, including the API key.

Troubleshoot the JumpCloud integration

Robin doesn't complete JumpCloud password resets

When a JumpCloud action doesn't run or fails, Robin tells the end user it couldn't complete the request. Check these causes:

JumpCloud isn't connected. Go to AI Center > Integrations > Product integrations and check that the JumpCloud card shows Active.
The connection is on a different customer. Robin uses the JumpCloud connection of the customer the ticket belongs to. Select that customer in Manage integrations for and check its JumpCloud card.
The email addresses don't match. Robin finds JumpCloud users by email address. Check that the end user's email address in Atera matches their email address in JumpCloud.
The end user didn't approve the action. Password resets and MFA resets are critical-risk actions. Robin runs one only after the end user approves that action in the conversation.
The user can't sign in with the temporary password. Check that Allow password change after expiration is on in JumpCloud (Settings > Security > Password Settings). Without it, JumpCloud blocks users whose password is expired, including the temporary password Robin sets.
The API key expired or was replaced. Generate a new key in JumpCloud, select the JumpCloud card in Atera, paste the key in API key, and select Update.

JumpCloud doesn't connect

When the connection fails, Atera shows Unable to connect to JumpCloud... please try again or contact support at support@atera.com, and the JumpCloud window shows Something went wrong and Check the details you entered and try again. Check these causes:

The API key is incomplete. Paste the full key you copied when you generated it. JumpCloud doesn't show a key again, so if you don't have it, generate a new one.
The API key's admin doesn't have API access. In JumpCloud, go to Settings > Administrators, select details for the admin, and check that Enable API access is selected.
The Organization ID is missing or wrong. Copy the Organization ID from Settings > Organization Profile in the JumpCloud organization you want to connect.
The Console URL doesn't match your region. Enter the console address for your region: console.jumpcloud.com (US), console.eu.jumpcloud.com (EU), or console.in.jumpcloud.com (India).

JumpCloud users don't appear in Atera

Synchronize users is off. Select the JumpCloud card, turn on Synchronize users, and select Update.
The import is still running. The first import can take a few minutes. After that, Atera updates JumpCloud users every 12 hours.
The sync didn't finish. If Atera shows JumpCloud settings saved, but user sync couldn't complete. Check your configuration and try again., check the connection details, then select Sync contacts from the JumpCloud card's menu.
The users have no email address. Check that the users have email addresses in JumpCloud.

JumpCloud integration FAQ

Can I sign in to Atera with JumpCloud through this integration?

No. This integration lets Robin and AI Copilot act on JumpCloud users and groups. Signing in to Atera with single sign-on (SSO) is a separate setting and isn't part of the JumpCloud integration.

Can Robin create or disable JumpCloud users?

Not on its own. Creating, enabling, and disabling users, creating groups, and changing group membership are AI Copilot actions for technicians. When an end user asks Robin for one, Robin either requests a technician's approval on the ticket or hands the ticket to a technician. To let Robin run one of these actions in a specific scenario, add it to a playbook step.

What happens when the JumpCloud API key expires?

The JumpCloud connection stops working, and Robin can't complete JumpCloud requests until you enter a new key. Generate a new key in JumpCloud, select the JumpCloud card in Atera, paste the new key in API key, and select Update.

How can we help?

Common topics:

MSP

IT Department

Related articles