# Docusign

![Image 1 of 1](https://assets.relyanceuat.xyz/images/docs/34756838770573/34756838766605.png)
DocuSign helps small- and medium-sized businesses collect information, automate data workflows, and sign on various devices.

The DocuSign integration will allow you to connect agreements in DocuSign with Relyance.

#### In the Relyance AI Application:

1. Login to your Relyance account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **DocuSign** 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**,

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34756838770573/37890688092557.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34756838770573/34756838767885.png)

9. In the Authentication section, provide the path of the folders where the contracts reside and select "**Enable Contract Scan**" for contract analysis along with Base URI and Account ID.
10. Review the configuration summary from the Completion section and click on Finish.
11. Confirm the integration Status reflects Connected

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34756838770573/37890683383565.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34756838770573/34756807102733.png)

The **Authentication** step asks for:

- **Path of the folders containing contracts delimited by; (Eg: folder1; folder2)**: required.
- **Base URI**: Account Base URI (Eg: https://demo.docusign.net); required.
- **Account ID**: Docusign Account ID; required; held as a secret.

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

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `signature`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. **A credential rotated at the vendor is not picked up here.** **Account ID** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
4. **Check the address fields before suspecting the credentials.** **Account ID** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

<!-- failure-modes:end -->

<!-- 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** | `Path of the folders containing contracts delimited by ;`, `Base URI`, `Account ID` (secret) | — |

<!-- 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 docusign/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

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