FAQ: eSignatures in Contract Management and Document Intelligence

Can I change the password of the administrator account that's connected to our eSignature integration without disruption?: If you change the password for the administrator account that was used to connect the eSignature integration in Contract Management and Document Intelligence, we suggest that you follow these steps to avoid issues:
Delete the current integration connection in Contract Management and Document Intelligence.
Reconnect the integration using the same account and the updated password.

Deleting the current connection cancels any active envelopes. This means that any existing signatures are removed.
Why do I get an authentication error when I collect signatures on a workflow ticket and then sign in to Adobe Sign through Okta?: This can occur if you're using Okta for your Adobe Sign account login and have not logged into Adobe Sign through Okta outside of Contract Management and Document Intelligence. To resolve this, sign in to Adobe:
Directly through your Okta integration outside of the Contract Management and Document Intelligence platform.
Through your Okta integration from within your Contract Management and Document Intelligence workflow ticket.
Why do some recipients not receive my custom DocuSign message?: When you use the
Actions
>
Edit Message
option to customize an email message for signers, this custom message might not append to your signature requests. You likely need to configure the
Enable custom email and language for each recipient
DocuSign setting in the
Sending Settings
area, and your DocuSign administrator must enable this option.

We recommend that you confirm with DocuSign Support or your in-house DocuSign administrator that enabling this feature won't impact your existing DocuSign processes.
In Workflow, what name is used on the eSignature request when collecting signatures?: We use the name configured on the account. In cases where signatures are collected by an individual user (each user has their own DocuSign/Adobe Sign login credentials), then the name differs depending on the user.

If configured to use a company account (a single account for the entire client), then the name associated with that account is used on the signature request.
Are changes to the signing order in DocuSign reflected on my ticket?: Changes to the signing order in DocuSign are reflected in Contract Management and Document Intelligence only for signer fields that must be completed during the signing process. For more information on configuring eSignature fields, see Concept: Workflow Builder Overview. If configured to use a company account (a single account for the entire client), then the name associated with that account is used on the signature request.
Do all signers, including the signing coordinator, have to sign in to the eSignature provider when collecting signatures in Workflow?: Unless you're the signing coordinator, you don't need to sign in to the eSignature provider when collecting signatures. When configuring the eSignature integration, you can require signing coordinators to sign in either individually or using the provided company account from the
Admin Console
. For both options, only the signing coordinator on a specific workflow must sign in to the eSignature provider when collecting signatures using either their individual account or company account credentials. They aren't required to sign in each time they collect signatures and aren't prompted to sign in again if they're already signed in. Other signers don't need to sign in.
Which eSignature providers integrate with Contract Management and Document Intelligence, and what are the account/license requirements?: Contract Management and Document Intelligence integrates with DocuSign and Adobe Sign. Signed documents are automatically added back to the workflow.

Contract Management and Document Intelligence doesn't support free DocuSign or Adobe Sign accounts, and accepts only paid, enterprise-level DocuSign or Adobe Sign accounts/licenses.