> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/d-j-integrations/jumpcloud-setup-for-workbench.md).
# JumpCloud Setup for Workbench
## Prerequisites
1. You must have admin access in Workbench to set up this integration.
2. You must have access to an account with **Administrator** privileges and API access enabled. *Note: Admins with the Billing role can enable API access for others.*
## Step 1: Create and Retrieve the JumpCloud API Key
The JumpCloud API Key is a secret key associated with an administrator account that grants full access to data accessible via the JumpCloud console. It is only displayed once when generated, so be sure to copy and save it immediately.
1. Log in to the [JumpCloud Console](https://console.jumpcloud.com/userconsole).
2. Select your account initials (or profile avatar) in the top-right corner.
3. In the dropdown menu, select **My API Key**. *If you do not see this option, contact an Admin with the Billing role to ensure API access is enabled for your account.*
4. Select **Generate New API Key**. You may be prompted to set an expiration date for the key. For a security integration, selecting an appropriate expiration date (e.g., 90 days) and planning for regular rotation is a best practice.
5. **Copy and save the generated API key in a safe place**. *This is the only time the full key will be visible, so be sure to copy and save it now.*
## Step 2: Add JumpCloud as a Security Device in Workbench
Now that you have the API key, you can add and configure the JumpCloud integration in Expel Workbench.
1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “Jumpcloud” and then select the **JumpCloud** integration.
5. A configuration pane displays. Complete the fields as follows:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName JumpCloud”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
* **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
* **JumpCloud API base URL** - leave "" populated in this field. *For EU tenants, enter "".*
* **JumpCloud API key** - enter the API key you saved in [Step 1](#step-1-create-and-retrieve-the-jumpcloud-api-key).
6. Select **Save**.
7. On the console access screen, select **No thanks, I will not provide console access from the dropdown**.
8. Select **Save**.
9. Your device should be created successfully within a few seconds. A few reminders:
* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team](/support/how-to-reach-us.md) for help.
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts tab** to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.expel.io/connect-your-technology/d-j-integrations/jumpcloud-setup-for-workbench.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.