Loading
Salesforce now sends email only from verified domains. Read More
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Configure a Salesforce Org for DocuSign Integration (Managed Package)

            You are here:

            1. Salesforce Help
            2. Docs
            3. Omnistudio for Managed Packages

            Configure a Salesforce Org for DocuSign Integration (Managed Package)

            For the managed package runtime, 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.

            Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

            • Enable OAuth 2.0 With Custom Settings In Omnistudio for Managed Packages (Managed Package)
              For the managed package runtime, salesforce recommends the more secure OAuth 2.0 for DocuSign. We've introduced a custom implementation for you to switch from OAuth 1.0 to OAuth 2.0 authentication for Omniscripts using custom objects (OmniScript__c). If you’re setting up DocuSign for the first time, you don't need to change the custom settings. If OAuth 2.0 authentication isn’t loading or you’re still using OAuth 1.0, enable OAuth 2.0 with the custom settings.
            • Create an Authentication Provider to Connect to DocuSign (Managed Package)
              For the managed package runtime, 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.
            • Create an OAuth 2.0 Named Credential to Connect to DocuSign (Managed Package)
              For the managed package runtime, 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.
            • Link Your Salesforce Org to Your DocuSign Account (Managed Package)
              For the managed package runtime, configure the DocuSign Admin page and create a Remote Site Setting for DocuSign so you can retrieve the templates from your DocuSign account.
            • Set Up Send on Behalf of Another User (Managed Package)
              For the managed package runtime, 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.
             
            Loading
            Salesforce Help | Article