> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# DocuSign

The **DocuSign** connector integrates Tess with DocuSign. Once connected, the AI can help check agreement status and support signature-related routines inside chats and agents.

DocuSign is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A DocuSign account with access to the envelopes/agreements you need.
  * Permission to authorize the DocuSign app for that account.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**. You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/docusign/01-connect-panel.png" alt="PRINT: (Connectors panel with DocuSign highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find DocuSign and click Connect">
    Under **Apps**, locate **DocuSign** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/docusign/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for DocuSign)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **DocuSign** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/docusign/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing DocuSign as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Check envelope/agreement status** for contracts in progress
* **Find agreements** by recipient, subject, or status when accessible
* **Support signature follow-ups** with clearer next steps
* **Help ops and legal-adjacent routines** stay coordinated in Tess
* **Reduce manual status checks** across inboxes and portals

## Example prompts

> 1. What is the status of the Acme MSA envelope in DocuSign?
> 2. List agreements waiting for signature for more than 3 days.
> 3. Summarize who still needs to sign the onboarding packet for Company Y.
> 4. Draft a polite reminder for the pending signer on the Acme MSA.

## Best practices

* Use unique agreement names or envelope IDs when possible.
* Ask before triggering send/void actions.
* In agents, define whether DocuSign is for status tracking or active envelope actions.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authorization fails" icon="circle-question">
    Reconnect with a DocuSign account that can access the needed envelopes and approve the app.
  </Accordion>

  <Accordion title="401 / connection dropped" icon="circle-question">
    Reconnect DocuSign in Connectors after credential or permission changes.
  </Accordion>

  <Accordion title="Envelope not found" icon="circle-question">
    Confirm the connected account can see that envelope in DocuSign.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>