Configure a Salesforce Org for DocuSign Integration

Enable Omnistudio to use DocuSign templates by configuring authentication providers, named credentials, and Omni Interaction Configurations. You can also enable sending or signing DocuSign documents on behalf of other users.

1. Create an Authentication Provider to Connect to DocuSign
   Add an authentication provider for Salesforce to create a secure connection to your DocuSign account. Omnistudio uses these credentials to fetch document templates from DocuSign.
2. Create an OAuth 2.0 Named Credential to Connect to DocuSign
   Add a Named Credential using authentication provider information to create a secure connection. Omniscripts and Integration Procedures use these credentials to connect with DocuSign. Create a named credential for the admin who manages templates and your DocuSign account. You can also create a Send on Behalf named credential to send or sign DocuSign forms on behalf of other users.
3. Add the DocuSign Login Page as a Trusted URL
   DocuSign runs on an iFrame. To allow the content to show on Experience Cloud sites, add the DocuSign login page as a trusted URL and allow iFrame content.
4. Add Omni Interaction Configuration Settings for DocuSign
   Provide DocuSign authorization by adding two Omni Interaction Configuration entries for DocuSign.
5. Set Up Send on Behalf of Another User for Omniscripts
   To send or sign DocuSign on behalf of another user, create a Send On Behalf field in the User object and assign the Send on Behalf named credential from that field in the user’s page. If you want multiple users to send or sign on behalf of another user, assign the named credential to each user. When you log in, Salesforce checks whether a Send On Behalf setup exists. If it doesn’t, Salesforce sends or signs DocuSign using the default admin user.