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

# Box

Learn how to configure a connection to Box with Couchdrop

## Overview

Couchdrop can connect directly to Box and make your Box files and folders available through Couchdrop.

Once connected, you can use Box with Couchdrop file transfer and workflow features while keeping files in your existing Box account.

## How to connect Box

{% hint style="warning" %}

### Before you start

To connect Box, you will need:

* A licensed Box account
* Team Admin access if you want Couchdrop to access folders belonging to other users in your Box organization
  {% endhint %}

{% stepper %}
{% step %}

### Add a new storage connection

In Couchdrop, add a new storage connection and select **Box** from the list of available connections.
{% endstep %}

{% step %}

#### Configure Box

Enter a **Name for this integration** and select the **Couchdrop folder path** where the connection will appear.

If you want to connect to folders belonging to other users in your Box organization, enable **As Team Admin**.
{% endstep %}

{% step %}

### Authorize Couchdrop

Select **Authorize Box** and sign in to Box when prompted.

Authorize Couchdrop to access Box on your behalf.

Couchdrop uses the Box APIs to list folder contents and upload, download, delete, and modify content stored in Box.

Select **Save and Test** to verify the Box connection.
{% endstep %}

{% step %}

### Map your Box storage location 

After the connection has been tested, you can optionally select a specific Box user or folder to map into Couchdrop.

Leaving this blank allows Couchdrop to map the Box connection without restricting it to a specific folder.

When a folder is selected, Couchdrop limits the connection to that location and its subfolders.
{% endstep %}

{% step %}

### Save and use your Box connection

Optionally, configure **Transfer Shield** to surface or block unexpected, non-compliant, or malicious files uploaded through this connection.

When the configuration is complete, save the integration.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>Do I need Team Admin access to connect Box?</summary>

No. Team Admin access is only required if you want Couchdrop to connect to folders belonging to other users in your Box organization.

</details>

<details>

<summary>Can I restrict Couchdrop to a specific Box folder?</summary>

Yes. After the connection has been tested, you can select a specific folder to map into Couchdrop. Couchdrop will then use that location and its subfolders for the connection.

</details>

<details>

<summary>Can Couchdrop connect to folders owned by other Box users?</summary>

Yes. Enable **As Team Admin** when configuring the connection if you need access to folders belonging to other users in the organization. Your Box account must have the required Team Admin access.

</details>

<details>

<summary>What access does Couchdrop require in Box?</summary>

Couchdrop requires authorized access to the Box APIs so it can list folder contents and upload, download, delete, and make changes to content stored in Box.

Couchdrop does not resell or share data obtained through the Box APIs.

</details>


---

# 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.couchdrop.io/storage/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.