DocuSign

OAuthProductivityOrg connection

Org-level connection

DocuSign is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

How to connect

In DocuSign Admin, go to Apps and Keys

Click "Add App and Integration Key", give it a name, and copy the Integration Key (a UUID) — this is your Integration Key

Under the app, click "Add Secret Key" and copy the generated value — this is your Secret Key

Enter the Integration Key and Secret Key above, and set the Environment to "production" for live accounts or "demo" for sandbox

Ready to connect?

Sign in to On Belay and open the Integrations page to add DocuSign.

Sign in →

Permissions (scopes)

These are the data scopes On Belay can be granted for DocuSign. Your org admin controls which scopes are enabled per group.

ScopeDescriptionAccess
signatureSend and manage envelopes and signaturesRead / Write

Troubleshooting

"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/docusign to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g. Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

Still stuck? We're happy to help.

Contact support →