> 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/l-p-integrations/okta-auth0-setup-for-workbench.md).
# Okta Auth0 Setup for Workbench
## Prerequisites
1. You must have an Auth0 user account with admin privileges to create the API keys.
## Step 1: Create a Custom API in Auth0
1. [Log in to the Auth0 dashboard](https://manage.auth0.com/).
2. Navigate to **Applications > APIs**.
3. Select **Auth0 Management API**.
4. Copy the "Identifier" URL **without the `/api/v2/ path` on the end** and save it in a safe place for use in a later step.
5. In the side navigation under Applications, choose **Applications** and select **Create Application**.
6. Choose **Machine to Machine Applications** and select **Create**.
7. On the Authorize Machine to Machine Application screen, select **Auth0 Management API** from the dropdown.
8. Assign the following permissions:
* read:logs\_users
* read:logs
* read:users
* read:user\_idp\_tokens
9. Select **Authorize**.
10. On the My App page, select the **Settings** tab.
11. Copy and save the **Client ID** and **Client Secret** values to a safe place for use in a later step.
## Step 2: Add Okta Auth0 as a Security Device in 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 the **Add Security Device** button.
4. In the search box, type “auth0” and then select the **Okta Auth0** integration.
5. Complete the fields as follows:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Auth0”; 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.
* **Auth0 URL** - enter the Auth0 Management API identifier without /api/v2/ on the end. For example, `https://companyname.us.auth0.com`.
* **Auth0 client ID** - enter the **Client ID** you saved earlier.
* **Auth0 client secret** - enter the **Client Secret** you saved earlier.
6. Select **Save**.
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 for help](/support/how-to-reach-us.md).
* 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/l-p-integrations/okta-auth0-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.