DocuSign

Connect DocuSign to collect digital signature evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In DocuSign:

   1. Sign in to your Docusign developer account and open the Apps and Keys page.
   2. Create an app (each app has exactly one integration key); in the Add API Integration Key dialog, enter an app name your users will recognize.
   3. Configure the app for one OAuth 2.0 grant: add a secret key and a redirect URI for Authorization Code Grant, or an RSA key pair for JWT Grant.
   4. Request an access token with the Docusign Admin scopes user_read and organization_read in addition to your eSignature scopes; calls to the Admin API fail if these scopes were not explicitly requested.
   5. Paste the resulting access token into Safeguard.

   Where to find the other values:

   • Account ID: The API Account ID is shown on the Apps and Keys page.
   • Environment (optional): Use production unless you are testing in the Docusign developer environment; an app's integration key is duplicated into production when you move the app there.

   DocuSign shows the secret only once, so copy it before you leave the page.

   DocuSign's public documentation does not cover every step.

   Docusign has no static API token: access tokens come from OAuth (Authorization Code Grant or JWT Grant) and expire, so a pasted token will stop working; JWT Grant with admin consent is the usual server-to-server path. Docusign also offers application-access tokens usable only for Admin API endpoints. Copy the secret key before you save the integration settings: Docusign says there is no way to go back and view it again after you close the window. Not sourced: where the Organization ID is shown (Docusign Admin), the role needed to create the app, the exact eSignature scope name, and the exact button that opens the Add API Integration Key dialog. The configure-app and Admin auth pages render client-side; they were read from their published page data.

   Source: developers.docusign.com, developers.docusign.com, developers.docusign.com, checked 2026-10-07.

   The permissions Safeguard needs: user_read, organization_read. Safeguard's compliance tests for DocuSign need the credential on the API token tab: an OAuth connection cannot read everything they check.

2. On Compliance › Connectors, open DocuSign, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   Organization ID	Required.
   Account ID	Required.
   Environment (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read DocuSign and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Digital Signature connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks