# Box

![2560px-Box__Inc._logo.svg.png](https://assets.relyanceuat.xyz/images/docs/34927413231629/34927413209101.png)
Box is an online file sharing and cloud content management service offering unlimited storage, custom branding, and administrative controls. The Box integration will allow you to connect one or many box folders with Relyance.

#### **In Box:**

1. Identify the folder IDs of the folders that need to be connected to Relyance - they will be required later in this procedure.
    - The folder ids are available in the URL (the number highlighted in the red box below)
    - Alternatively, if you would like to provide Relyance access to all folders, use the id “0” in the configuration in Relyance as described below.

    ![image6.png](https://assets.relyanceuat.xyz/images/docs/34927413231629/34927429550221.png)

#### **In Relyance:**

![mceclip0 (1).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36478879398669.png)
1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Box** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see[Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    1. **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    2. **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    3. **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the following information retrieved from the **Box** section and click on **Continue**.
    - **IDs of the folders containing contracts delimited by ';'**
        - **Eg: 140515; 320273**
    - Select the **Enable Contract Scan** checkbox in order to retrieve contracts from this integration
    - Once you click on authenticate it will redirect to the box for authentication where you have to enter username and password or use SSO to authenticate.  Then once you are authenticated, it will redirect you to another page where you need to click on Grant access and give your consent.  Once you click on Grant access, the authentication will be successful and it will be redirected to Relyance page.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
    - **Sampling Percentage:** This property adjusts the percentage of records using the table's row count (1000 records max) to return from a table.
11. Review the configuration summary from the **Completion** section and click on **Finish.**

![mceclip1 (1).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461012429453.png)

![Screenshot 2025-05-08 at 10.28.30 PM.png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461012430477.png)

![image (1).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461000587021.png)
![Screenshot 2025-05-08 203142 (1).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461000587661.png)

![mceclip4 (1).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461000588045.png)

![image (2).png](https://assets.relyanceuat.xyz/images/docs/34927413231629/36461000588685.png)

12. Confirm the integration Status reflects **Connected**

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Oauth2 / App Token** | `IDs of the folders containing contracts delimited by ;` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example box/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

<!-- terraform-examples:end -->