You are here:
Workflow to Setup E-Signature for Contract Object
System admin must integrate DocuSign with Salesforce Contracts for users to be able to email a copy of the document to sign at the recipient’s convenience. DocuSign integration requires an active DocuSign account.
System admin must enable Salesforce Contracts to use DocuSign by configuring these settings:
To send documents generated from standard and custom objects other than a contract, you use a different process. For details, see Workflow to Setup E-Signature for Standard and Custom Objects.
- Permission Sets For DocuSign
The system admin must assign either the Contract Management (Salesforce Contracts) or DocGen permission set licenses to your user to send documents for e-signature. Non-Salesforce Contracts users must be assigned a DocGen license. - Create an Auth Provider for DocuSign
Add an Auth Provider credential for DocuSign in Salesforce to create a secure connection. Omnistudio uses these credentials to fetch document templates from DocuSign. - Create a Named Credential for DocuSign
Add a Named Credential using auth provider information to create a secure connection. Omniscripts and Integration Procedures use these credentials to connect with DocuSign. - Electronic Signature Configuration
Using the Electronic Signature Configuration setup, the system admin must define the required configurations to support the e-signature APIs and UI. - Default Contract Type Config Settings for E-Signature
Salesforce Contracts application provides a default set of signature settings for the contract such as defining the default reminders and expiry warnings for the envelopes submitted for e-signatures. - Set Up the Remote Site
To configure DocuSign to work with the Salesforce Contracts application, you must connect Salesforce to a DocuSign account. You set up the DocuSign remote site as one of the websites your Salesforce org can invoke.

