DocuSign Settings Recommendations
DocuSign is used in the DocuSign Signature Phase. The integration between symplr Contract and DocuSign allows for some degree of automation, but there are limits to which DocuSign features can be supported by symplr Contract in the context of integration.
Generally speaking, symplr Contract relies on having sequenced DocuSign participants perform their actions in the order defined on the Signature Phase.
Any DocuSign envelope will work and sync correctly if the user who starts the phase (the Phase Owner, Phase Mediator, or Admin) does only the following when the phase starts:
Places the necessary DocuSign tabs (Signature, Initials, Dates, etc.) on the documents that were transferred from symplr Contract.
Clicks Send.
DocuSign offers many more features, though, and depending on the Administrative settings, DocuSign may allow the users to make changes that are incompatible with an automated sync-back with symplr Contract. For example, a sender could:
Insert additional Signers
Resequence Signers
Change the level of participation (e.g., change a Signer to a cc recipient)
Add additional documents to the envelope
Remove documents from the envelope
Switch to an un-sequenced signing experience
Any of these actions have the potential to create a syncing error. The following DocuSign account setting recommendations optimize the symplr Contract and DocuSign integration.
Customers who use their own DocuSign account outside of symplr Contract may have needs that conflict with these recommendations. Given that customers use DocuSign in several ways that are unrelated to the symplr Contract integration, this is expected.
Account > Security Settings
Setting | Section | Recommendation | Notes |
---|---|---|---|
Recipient Authentication Settings | Authentication Settings | Disable Recipient Authentication for this account | If enabling, please ensure an understanding of the implications, particularly with regard to Other Party Signatories. By default, DocuSign does not require Signers to have DocuSign accounts, and this is one of the reasons it is so universally accepted. |
Password Rules | Password Security | N/A | Use the default or whatever is appropriate for the organization’s security policies. |
Allow user to edit their name | User Personal Information | Disable | If Signers are using logins on the integrated DocuSign account, this could potentially create a mismatch between DocuSign and symplr Contract users. |
Signing and Sending > Signing Settings
Setting | Section | Recommendation | Notes |
---|---|---|---|
In Session Landing Pages | Signing Experience | N/A |
|
Watermark Configuration | Signing Experience | N/A |
|
Auto-Navigation | Signing Experience | N/A | Although any of these selections are okay, Navigate Required Fields is generally what symplr Contract uses for testing, and it improves user experience. |
Require a reason when a recipient declines to sign | Recipients | Enabled | This reason will be recorded in symplr Contract. Requiring this field better documents the reasons why a particular workflow needed to be retracted or canceled. |
Allow recipients to sign on paper | Recipients | Disabled | If the recipient understands how to complete the upload process using DocuSign, the merger of ink and digital signatures will work seamlessly. If the recipient decides to mail, email, or fax the document back, though, it will require a great deal of work to correct everything. |
Allow senders to override sign on paper | Recipients | Disabled | If the recipient understands how to complete the upload process using DocuSign, the merger of ink and digital signatures will work seamlessly. If the recipient decides to mail, email, or fax the document back, though, it will require a great deal of work to correct everything. |
Allow recipients to sign on a mobile device | Recipients | N/A |
|
Allow recipients to change signing responsibility | Recipients | Disabled (strong recommendation) | These changes will generally not sync with symplr Contract. |
Allow senders to override change signing responsibility | Recipients | Disabled (strong recommendation) | These changes will generally not sync with symplr Contract. |
Allow recipients to edit documents | Recipients | Disabled | The DocuSign markup will sync with symplr Contract, but using it effectively will require some degree of planning and training. Ideally, all negotiations would take place in symplr Contract prior to the Signature Phase. |
Allow recipients to create a DocuSign account | Recipients | N/A |
|
Allow offline signing on a mobile device | Recipients | N/A | This setting refers to users associated with the DocuSign account. |
Allow recipients to sign documents offline on a mobile device | Recipients | N/A | This setting refers to envelope recipients who aren’t users on the account. |
Ask for confirmation if recipients try to leave an active signing session | Recipients | N/A |
|
Remind recipients to finish the signing session after they fill in required fields | Recipients | N/A |
|
Allow recipients to assign delegated Signer | Delegation | Disabled (strong recommendation) | This is conceptually similar to proxy functionality in symplr Contract, which is the preferred way to handle any Out of Office time. Any envelopes with delegated Signers processed through DocuSign will not sync correctly. |
Apply the following formats to the Date Signed field: | Document Formatting | N/A |
|
Signature Adoption Configuration (link) | Signature | Lock Recipient Name N/A on all other settings | Name typos should be corrected in symplr Contract. A name mismatch between symplr Contract and DocuSign will not cause a technical sync failure, but it will result in two distinct names in the two systems. |
Apply the selected format to the Signature field | Signature | N/A |
|
Attach documents to completion email | Envelope Delivery | N/A |
|
Attach certificate of completion to envelope | Envelope Delivery | N/A | The certificate will not automatically sync back to symplr Contract, but it will be available in the DocuSign account. |
Suppress emails to embedded Signers | Envelope Delivery | N/A | symplr Contract does not support embedded signing, where signing takes place within a host application. It only supports remote signing, where Signers have the option of referencing envelopes in their own DocuSign accounts. |
Send completion emails to embedded Signers | Envelope Delivery | N/A | symplr Contract does not support embedded signing, where signing takes place within a host application. It only supports remote signing, where Signers have the option of referencing envelopes in their own DocuSign accounts. |
Signing and Sending > Sending Settings
Setting | Section | Recommendation | Notes |
---|---|---|---|
Default font for fields | Fields and Properties | N/A |
|
Enable formula field (calculated field) | Fields and Properties | N/A |
|
Enable conditional fields | Fields and Properties | N/A |
|
Allow Admins to share custom fields | Fields and Properties | N/A |
|
When an envelope is sent, write the initial value of the field for all recipients | Fields and Properties | N/A |
|
Allow fax delivery to recipients | Fields and Properties | Disabled | If the recipient understands how to complete the upload process using DocuSign, the merger of ink and digital signatures will work seamlessly. If the recipient decides to mail, email, or fax the document back, though, it will require a great deal of work to correct everything. |
Enable Signer attachment field | Fields and Properties | Disabled | These attachments won’t prevent syncing, but the attachments themselves will not sync back to symplr Contract. The attachments will be available in the DocuSign account. |
Document Visibility | Fields and Properties | N/A | DocuSign considers this a premium feature, and it therefore won’t be available on all accounts. Customer-owned accounts can contact DocuSign to upgrade to make use of this. |
Enable draw new signature for each signature or initial field | Fields and Properties | N/A |
|
Allow senders to require Signers to upload a new image to sign or initial | Fields and Properties | N/A |
|
Prevent users from forwarding completed envelopes | Fields and Properties | N/A |
|
Enable signature stamp field | Fields and Properties | N/A |
|
Enable signature stamp field | Fields and Properties | N/A |
|
Enable including the Envelope ID on the document | Fields and Properties | N/A |
|
Automatically replicate information in fields with the same Data Label | Fields and Properties | N/A |
|
Allow sender to download form data | Fields and Properties | N/A |
|
Enable custom email and language for each recipient | Fields and Properties | N/A | This can only be manually edited in the DocuSign UI, and it will not affect the sync. |
Allow senders to add recipients from this account's User Directory | Fields and Properties | N/A |
|
Enable envelope copy with field data | Fields and Properties | Disabled | While some users might find a use for this feature when complex envelopes get declined, all of that work would need to take place outside of symplr Contract (solely in DocuSign) and then be added to symplr Contract after the fact. No copies of envelopes would ever sync automatically back to an symplr Contract workflow. |
Enable bulk recipients | Recipient Roles | Disabled | No bulk sending (sending independent copies of a single document to many people) of any kind will sync with symplr Contract. |
Enable needs to view role | Recipient Roles | Enabled (strong recommendation) | Any use of sequenced non-signatory participants (e.g. Reviewers and Approvers) in a DocuSign Signature Phase requires that this be enabled. If the setting is disabled, and non-signatory participants are sequenced, the envelope will not send to Docusign correctly, and an error will appear. |
Enable specify recipients | Recipient Roles | Disabled (strong recommendation) | Modifying the recipients and the sequence of those recipients is likely to cause a problem syncing the envelope back to symplr Contract. |
Enable allow to edit recipient | Recipient Roles | Disabled (strong recommendation) | This option gives a recipient the ability to edit the entire envelope (documents, recipients, expiration rules, etc.). Depending on what changes are made, it is probable that a syncing issue with symplr Contract could be created. A safer approach would be for the Phase Manager or Admin starting the digital Signature Phase instead reach out directly to the would-be envelope editor to discern any envelope setting details that only they can provide. |
Enable update recipients | Recipient Roles | Disabled (strong recommendation) | This option allows an envelope recipient to change future recipients, which could cause a syncing issue with symplr Contract. |
Enable in person (hosted) signing role | Recipient Roles | Disabled (strong recommendation) | As this affects the participant roles, it is likely to create a problem with syncing back to symplr Contract. |
At this time, we do not have recommendations for the following settings:
Account > Regional Settings
Account > Brands
Users and Groups > Users (we suggest leaving the integration account user enabled as an Admin)
Users and Groups > Permission Profiles
Users and Groups > Groups
Signing and Sending > Signing Settings
Signing and Sending > Email Preferences
Signing and Sending > Custody Transfer
Signing and Sending > Document Retention
Signing and Sending > Legal Disclosure
Signing and Sending > Reminders and Expiration