> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-nhi-visibility-draft.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Docusign connector

> C1 provides identity governance for Docusign. Integrate your Docusign instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

<Tip>
  **This is an updated and improved version of the Docusign connector!** If you're setting up Docusign with C1 for the first time, you're in the right place.
</Tip>

## Capabilities

| Resource                          | Sync                                                            | Provision                                                     |
| :-------------------------------- | :-------------------------------------------------------------- | :------------------------------------------------------------ |
| Accounts                          | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups                            | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Signing groups                    | <Icon icon="square-check" iconType="solid" color="#c937ae" />\* | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Permission profiles               | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| CLM members, roles & groups\*\*   | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | Groups only                                                   |
| CLM folders & folder security\*\* | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| CLM permission sets\*\*           | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-xmark" iconType="solid" color="#c937ae" /> |
| CLM workflow queues\*\*           | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-xmark" iconType="solid" color="#c937ae" /> |

The Docusign connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning).

Every Docusign account must be assigned at least one permission profile. If all other permission profiles are revoked, the account will be automatically assigned the **DocuSign Viewer** profile, which cannot be revoked.

\*By default, signing groups are not synced. Enable the **Include Signing Groups** setting to sync signing groups. Once enabled, your account must actually have the signing groups feature — ConductorOne doesn't validate this before letting you turn the setting on, so enabling it without the feature will fail the sync rather than silently sync no signing groups.

\*\*DocuSign CLM (Contract Lifecycle Management) is a separate, separately-licensed DocuSign product. CLM resources are opt-in — enable each CLM resource type in your sync configuration to turn them on. Once enabled, your DocuSign account must have a CLM production subscription and the credential must have been granted the OAuth scopes CLM needs; enabling a CLM resource type without them will fail the sync rather than silently sync no data, since ConductorOne doesn't validate the underlying subscription before letting you opt in. CLM permission sets and workflow queues sync for visibility only; DocuSign's CLM API has no endpoint to assign or unassign a permission set, and no endpoint to grant or revoke workflow queue membership (only work-item assign/unassign, which isn't synced here). CLM workflow queues also require CLM members to be enabled — queues are discovered per member, not via a standalone list endpoint.

<Warning>
  If you use **OAuth Authentication** (the default, managed method), syncing CLM data requires ConductorOne's managed OAuth app to be granted the CLM API scopes on the platform side. If CLM data doesn't appear after setup, contact ConductorOne. This doesn't apply to **Custom App (Demo Environment)**, where the connector requests the CLM scopes directly using your own DocuSign app credentials.
</Warning>

## Gather Docusign credentials

Configuring the connector requires you to pass in credentials generated in Docusign. Gather these credentials before you move on.

The Docusign credentials requirements depend on your chosen hosting method and authentication mode:

* **Cloud-hosted (production)**: You'll use C1's managed OAuth app. No additional credentials are needed. You can **skip this section** and go straight to the cloud-hosted setup instructions below.

* **Cloud-hosted (demo environment)** or **Self-hosted**: You'll need to create a Docusign developer app. Go on to the next section.

### Create a Docusign app

<Warning>
  A user with access to the **Docusign Admin console** must perform this task.
</Warning>

<Steps>
  <Step>
    In the Docusign Admin Console, click **Add App and Integration Key**.
  </Step>

  <Step>
    Choose a name for your app, such as "C1" and click **Create App**.
  </Step>

  <Step>
    On the app configuration screen, carefully copy and save the **Client ID** (also called an integration key).

    You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications). The key is created and used against your own DocuSign account in both hosting modes, so **Private custom integration** — DocuSign's description is *"used internally by your employees or your customers' employees"* — matches most setups. If you're going through C1's **Custom App (Demo Environment)** field group, you may instead consider **Third-party integration key** — *"using a partner integration that requires your own integration key"* — since C1 is the party invoking it on your behalf; confirm with DocuSign which classification fits your situation before proceeding, since it isn't reversible.
  </Step>

  <Step>
    Click **Add Secret Key**, then carefully copy and save the client secret.
  </Step>

  <Step>
    In the **Redirect URI** field:

    * If you're configuring a **self-hosted** connector, enter any URI of your choice (such as [http://example.com/callback](http://example.com/callback)) and click **Add**. Nothing needs to be listening at that address — the `--configure` flow prints an authorization URL, and after you authorize, DocuSign redirects your browser there; copy the `code` parameter from the resulting (unreachable) URL and paste it when prompted. Whatever value you register here must also be passed as `--redirect-uri` / `BATON_REDIRECT_URI`, or the authorization and token exchange will fail.
    * If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1 completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here.
  </Step>

  <Step>
    Under **Authentication**, enable **Authorization Code Grant**.
  </Step>

  <Step>
    Click **Save** at the bottom of the page.
  </Step>
</Steps>

#### Generate an OAuth refresh token

<Steps>
  <Step>
    Follow the [Docusign instructions to generate a refresh token](https://developers.docusign.com/platform/auth/confidential-authcode-get-token#use-refresh-tokens).
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

## Configure the Docusign connector

<Warning>
  To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1 and the relevant set of permissions on your Docusign account:

  * To sync access data (READ): Read users, groups, and permissions.

  * To sync access data and provision accounts (READ/WRITE): Create users plus read users, groups, and permissions.

  * To sync CLM data: your DocuSign account needs a CLM production subscription, and the credential used must have read (and, for folder security and CLM group provisioning, write) access to CLM folders, groups, and members.
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Docusign v2** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Docusign connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Choose your **authentication method**:

        * **OAuth Authentication** (default) — connects to DocuSign's production environment using C1's managed OAuth app. No additional credentials required.
        * **Custom App (Demo Environment)** — connects to DocuSign's demo environment (`account-d.docusign.com`) using your own DocuSign developer app. See [Create a Docusign app](#create-a-docusign-app) above to obtain your credentials.
      </Step>

      <Step>
        **If you selected Custom App (Demo Environment):** Enter the **Client ID** and **Client Secret** from your DocuSign developer app.
      </Step>

      <Step>
        **Optional.** Click to **Sync signing groups**, if your account has the feature enabled and you'd like to sync them.
      </Step>

      <Step>
        **Optional.** If your organization has multiple DocuSign accounts under the same tenant, enter the **API Account ID** (UUID) of the account you want to sync. Leave blank to use your default account. To sync multiple accounts, create a separate connector for each one.

        <Warning>
          Do not change the **API Account ID** to a different account on a connector that is already syncing. Doing so will cause all previously synced resources to be treated as deleted and all sync history will be lost. If you need to sync a different account, create a new connector instead.
        </Warning>
      </Step>

      <Step>
        Click **Login with OAuth**.
      </Step>

      <Step>
        Log in and authorize C1 with your Docusign instance.
      </Step>

      <Step>
        After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Docusign connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Docusign connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [Official download center](https://dist.conductorone.com/ConductorOne/baton-docusign): For stable binaries (Windows/Linux/macOS) and container images.

    * [GitHub repository](https://github.com/conductorone/baton-docusign): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Docusign connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Docusign connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Docusign connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-docusign-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-docusign-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Docusign credentials
      BATON_DOCUSIGN_CLIENT_ID: <Docusign app client ID>
      BATON_DOCUSIGN_CLIENT_SECRET: <Docusign app client secret>
      BATON_REDIRECT_URI: <The redirect URI you entered when setting up the Docusign app>
      BATON_REFRESH_TOKEN: <OAuth 2.0 refresh token>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true

      # Optional: include if you want C1 to sync signing groups
      BATON_INCLUDE_SIGNING_GROUPS: true

      # Optional: set to true to connect to the DocuSign demo/UAT environment (account-d.docusign.com)
      # When omitted or false, the connector targets DocuSign production (account.docusign.com)
      # Note: demo mode is automatically enabled when BATON_DOCUSIGN_CLIENT_ID is set.
      BATON_DEMO: true

      # Optional: API Account ID (UUID) of the DocuSign account to sync.
      # Leave blank to use your default account.
      # Required only if your organization has multiple DocuSign accounts.
      # Find it in DocuSign Admin → Apps and Keys → My Account Information → API Account ID.
      # WARNING: do not change this value on an existing connector — create a new connector instead.
      BATON_ACCOUNT_ID: <DocuSign API Account ID>
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-docusign.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-docusign
      labels:
        app: baton-docusign
    spec:
      selector:
        matchLabels:
          app: baton-docusign
      template:
        metadata:
          labels:
            app: baton-docusign
            baton: true
            baton-app: docusign
        spec:
          containers:
          - name: baton-docusign
            image: public.ecr.aws/conductorone/baton-docusign:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-docusign
            envFrom:
            - secretRef:
                name: baton-docusign-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Docusign connector to. Docusign data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Docusign connector is now pulling access data into C1.
  </Tab>
</Tabs>