To minimize the administrative burden on your users, it is recommended that you grant consent to your application administratively using Blanket Consent. Blanket Consent enables an authorized organization administrator to grant consent to the client ID on behalf of individual users. 

Only use this if you are using the Admin Consent flow.

To use Administrative Consent: 

  • Your account must include the Access Management with SSO feature. Note that administrative consent does not require that you install SSO, but you do need the product feature which includes SSO. For testing purposes, if your developer demo account does not include the feature, you can contact DocuSign at go-live@docusign.com and request that the feature be added to your account. Be sure to provide your Developer Demo Account ID.
  • You must claim your email DNS domain via the DocuSign administration tool. A domain can be claimed both by the DocuSign developer demo system and by your production DocuSign account. 
  • Your users' email domains must match the claimed email domain. 
  • Your integration keys management account must be one of the accounts in the DocuSign organization. 

A DocuSign Admin (not an eSignature Admin) can then grant consent to your applications client ID administratively. Remember to grant consent for both the signature and impersonation scopes. 

Custom Button to Grant Consent

As an Administrator, create a custom button to grant consent manually using the following steps.

  1. Go to Salesforce Setup > Create > Objects > Agreement  
  2. Create a new Custom Field, field type set as Formula. 
  3. Fill out the Label Name and API Name fields. 

  4. Insert the following formula: 

    HYPERLINK('https://account-d.docusign.com/oauth/auth?response_type=code&scope=impersonation signature&client_id=<Integrationkey>&redirect_uri=<redirectUrl>', IMAGE("<Static Resource Button Image Path>","Grant Consent"), "_self")
    CODE

    The above base URL 'https://account-d.docusign.com' is for a Demo DocuSign account. For production environments, use 'https://account.docusign.com'.
    You can use an optional parameter State, if you want the user to be redirected to send for eSignature or any other custom page. To include this parameter in HYPERLINK formula, use the following syntax:

    &state=Apttus_CMDSign__CMDocusignManageEnvelope:<agreementId>
    CODE
  5. For the <Static Resource Button Image Path>, use any button image you choose and upload it as a static resource.
  6. The Administrator has to specify the integration key and redirect URL. The redirect URL should be your Salesforce Instance URL (also referred to as your base URL) of your Organization and must be registered in your DocuSign Account Settings. You can find your base URL by following these instructions here. 

Setting up One-Click Send and Individual Consent

As this feature is part of the DocuSign-CLM and DocuSign-CPQ integration, Conga supplies the following workaround to resolve a problem encountered using the one-click send feature and DocuSign's individual consent, because consent is required prior to calling the DocuSign API.

  • Get an admin consent license from DocuSign and it will support one-click send without any issue.
  • If you are unable to get an admin consent license from DocuSign, the Administrator can set up a custom field as referenced in Custom Button to Grant Consent. Your Administrator will need to train DocuSign users to first grant consent by clicking on the custom field. 
  • Your Administrator can send a mass email to your DocuSign users to click the grant consent link, as referenced in Custom Button to Grant Consent.
  • If you are unable to apply any of the previous three options, a fix can be applied readily in the DocuSign-CLM/DocuSign-CPQ package, and you can upgrade to this package. 

If you are upgrading DocuSign-CLM integration, you will need to update to the following version: Apttus Contract Management (Apttus) 12.0.0605.9 (12.605.9) or higher.

If you are upgrading DocuSign-CPQ integration, you will need to update to the following version: Apttus Proposal Management (Apttus_Proposal) 6.5.0071 (6.71) or higher.