> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/integrations/box.md).

# Box

Box is a cloud-storage company used by 97,000 organizations, including a critical mass of Fortune 500 companies. Box allows its users to access information from anywhere and collaborate with anyone.

## Use cases

Integrate Box with DoControl to make smarter decisions and reduce security risk in the following ways:

* **Get full inventory visibility -** Capture data about users and assets located in all folders across your organization
* **Trigger alerts** - Get real-time event notifications for anomalous activity and file overexposure, such as, external or public sharing of sensitive files, 4th party sharing, extensive file downloads, former employees downloading or sharing assets, sharing assets with or by a malicious domain
* **Remediate past exposure** - Leverage on-demand bulk remediation, such as remove shared links, remove external collaborators
* **Remediate future exposure** - Define automated security workflows with these remediation actions:

  * **Remove a collaborator** - You can remove collaborator access from a Box file for one or more collaborators. When an asset exists in a parent folder, collaborator access is removed from all assets in the folder.&#x20;
  * **Remove shared links** - You can remove shared links from an asset in Box.
  * **Add a collaborator** - After DoControl automatically removes a collaborator, you can restore the collaborator after confirmation.

  You can also set up smarter workflows, for example, to be notified when encryption key files are uploaded.

## Prerequisites  <a href="#prerequisites" id="prerequisites"></a>

* The user performing the DoControl-Box integration must have one of these admin privileges:
  * **Admin** - principal account administrator of Box. Your Box account can be any business plan.
  * **Co-admin** - Co-admins cannot perform the same duties as the Admin user. They can integrate and perform actions only on users that are not admin or other co-admins. Your Box account plan must be either **Business Plus** or **Enterprise**.

{% hint style="warning" %}

* Group admins cannot integrate Box with DoControl.
* Co-admin users do not have access to data (assets) that is owned by other co-admin and admin accounts.
* For more information about co-admin privileges, see [Box support](https://support.box.com/hc/en-us/articles/360043693434-API-Content-API-403-access-denied-insufficient-permissions-Errors).
  {% endhint %}

Before starting to integrate, you need to sign up with DoControl. Follow the onboarding steps in [Create first account](/docontrol-user-guide/getting-started/quick-start/set-up-docontrol-basics.md#create-first-account).

## Permission scopes

For more information on Box prerequisites, see [permission scopes](https://developer.box.com/guides/api-calls/permissions-and-errors/scopes/) and [events](https://developer.box.com/reference/resources/event/).

## Integrate Box with DoControl

![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fjq9y38DvZBwqCcQKgThG%2Fimage.png?alt=media\&token=5d2ced8c-ffba-4dff-9dd4-9e9163ca38e8)

1. From the DoControl side menu, click **Integrations**.
2. Under **Box**, click **Connect**.&#x20;
3. Enter your Box credentials, then click **Grant access to Box**. \
   You are returned to the DoControl **Integrations** page, and Box is now integrated.

## Troubleshooting

Q. What happens if my Box token expires?

A. If the person who performed the integration leaves your organization, your Box token will expire. You need to reconnect to DoControl by performing the [integration procedure](#integrate-box-with-docontrol) again.

Q. I don't manage to integrate Box. Is there a permission issue?

A. If you don't succeed in integrating Box with DoControl, check that your Box **co-admin** user has been granted all the required permissions:

<table><thead><tr><th width="279">Box parameter</th><th>Administrative privileges</th></tr></thead><tbody><tr><td>Users and groups</td><td><ul><li>Manage users</li><li>Manage groups</li></ul></td></tr><tr><td>Files and folders</td><td><ul><li>View users' content</li><li>Edit users' content</li><li>Log in to users' accounts</li></ul></td></tr><tr><td>Reports and settings</td><td><ul><li>View settings and apps for your company</li><li>Edit settings and apps for your company</li><li>Run new reports and access existing reports</li></ul></td></tr><tr><td>Metadata</td><td><ul><li>Create and edit metadata templates for your company</li></ul></td></tr></tbody></table>

{% hint style="info" %}
For more information, see [Box support documentation](https://support.box.com/hc/en-us/articles/360044194393-Granting-And-Modifying-Co-Admin-Permissions).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/integrations/box.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
