> 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/dropbox-setup-for-workbench.md). # Dropbox Setup for Workbench ## Step 1: Enable API Access for Workbench To integrate the technology with Workbench, you need to create secure credentials to the API. 1. Log in to . 2. For Choose an API, select **Scoped access**. 3. For Choose the type of access you need, select **Full Dropbox**. 4. Give your app a name in the following format: "Expel - \". 5. Click **Create app**. 6. Go to the Permissions tab and grant the token the following permissions: * **Account Info** - `account_info.read` * **Files and folders** - `files.metadata.read` * **Team Data** - `team_data.member` * **Members** - `groups.read` * **Sessions** - `sessions.list` and `events.read` 7. Click **Submit** at the bottom of the page. 8. Go to the recently created app and **copy and save** the **App Key** and **App Secret** in a safe place for use in a later step. 9. Paste the below Dropbox OAuth authorize URL (with your `` substituted in) into your browser. You must be logged in for this to work. ``` https://www.dropbox.com/oauth2/authorize?client_id=&response_type=code&token_access_type=offline ``` 10. Click **Continue** and **Allow**. 11. Copy the **Authorization Code** provided on the next screen. 12. In your CLI, run the request to the [Dropbox `oauth/token` endpoint](https://www.dropbox.com/developers/documentation/http/documentation#oauth2-token), substituting your Authorization Code for ``, your App Key for ``, and your App Secret for `:` ``` curl -d "code=" -d "grant_type=authorization_code" -d "client_id=" -d "client_secret=" -X POST https://api.dropbox.com/oauth2/token ``` {% hint style="warning" %} Make sure to use your Authorization Code, App Key, and App Secret in the request before continuing. Also make sure your CLI is on a trusted device, since you are including your key and secret key. {% endhint %} 13. Copy the `refresh_token` from the JSON response value to add to Workbench in [Step 2](#uuid-22b274e8-6c96-e6f6-20f7-f9c32889be90_bridgehead-26196). Example response:\ `{'access_token': '', 'token_type': 'bearer', 'expires_in': 14400, 'refresh_token': , 'scope': 'account_info.read events.read files.metadata.read groups.read sessions.list team_data.governance.read team_data.governance.write team_data.member', 'uid': '', 'team_id': 'team-id'}` ## Step 2: Add Dropbox as a Security Device 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/auth/login?orig=%2F). 2. In the side menu, navigate to **Organization Settings** > **Security Devices**. If you have multiple organizations, you must select the appropriate organization name from the list. 3. Select **Add Security Device.** 4. Search for and select **Dropbox**. * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Dropbox”; 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. * **API token** - leave blank. * **Refresh Token** - paste the generated token value from [Step 1](#uuid-22b274e8-6c96-e6f6-20f7-f9c32889be90_bridgehead-26158). * **Application ID** and **Application Secret** - paste the key and secret values from [Step 1](#uuid-22b274e8-6c96-e6f6-20f7-f9c32889be90_bridgehead-26158).
Dropbox Add a Security Device screen in Workbench.
5. 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/d-j-integrations/dropbox-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.