> 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/a-c-integrations/box-setup-for-workbench.md).
# Box Setup for Workbench
## Prerequisites
1. You must have a Box enterprise admin user with access to the [Developer Console](https://app.box.com/developers/console) and [Admin Console](https://app.box.com/master/custom-apps) to build and authorize a Custom App.
## Step 1: Enable API Access for Workbench
1. Sign in to your Developer Console.
2. Select **Create New App**.
3. Select **Server Authentication (Client Credentials Grant)**.
4. Name your custom app "Expel" and click **Create App**.
5. Click **Fetch Client Secret** and make note of the **Client ID** and **Client Secret** as you only see it one time.
6. Select the app access level **App + Enterprise Access**.
7. Select the following application scopes:
* Read all files and folders stored in Box.
* Manage enterprise properties.
8. On the **Authorization** tab, select **Review and Submit for app authorization**. The app status now reads `Pending Authorization`.
9. Authorize the app through email or sign in to your Admin Console and click **Apps** on the top-left side of the page.
10. Under Custom Apps, find the app that was submitted and select **Authorize App**.
11. Navigate to **Account & Billing** from the top left side of the page and take note of your **Enterprise ID**.
## Step 2: Configure the Technology in Workbench
Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.
1. [Log in to Workbench](https://workbench.expel.io/).
2. Navigate to **Settings > Security Devices**.
3. At the top of the page, click **Add New Device**.
4. Search for and select **Box**.
5. A configuration pane displays. Complete the fields as follows:
1. **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Box”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
2. **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.
3. **Client ID** - enter the client ID you saved in [Step 1](#uuid-86af3bf2-d920-f98a-54c2-9055e60c39ad_bridgehead-23671-1).
4. **Client secret** - enter the secret you saved in [Step 1](#uuid-86af3bf2-d920-f98a-54c2-9055e60c39ad_bridgehead-23671-1).
5. **Enterprise ID** - enter the Enterprise ID you saved in [Step 1](#uuid-86af3bf2-d920-f98a-54c2-9055e60c39ad_bridgehead-23671-1).
6. Click **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/a-c-integrations/box-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.