Skip to main content
Conga Support

DocuSign Self Service implementation

You can specify your own DocuSign  endpoints

You can switch your Conga Contracts system instance between separate DocuSign instances. For example, you might have a production and a sandbox version of DocuSign running in your Conga Contracts instance so you have the option to connect the sandbox to your Conga Contracts instance to test DocuSign functionality before you switch to your production instance.

Self Service Docusign settings management

You can manage your Docusign integration settings like usernames, passwords and other security features in the user interface. 

When you select Admin > System Settings > Integration Settings, you see the following field options: The following Docusign Account ID, Docusign Account Name, Docusign Username, and Docusign Password. The values relate to the fields with the exception of Docusign Password, match the values in the UserCompany table in the Conga Contracts database.

Self Service Docusign templates 

You can use any company designated DocuSign templates. An administrator can select a template on the request type or in the New Contracts area. The template is validated with DocuSign to ensure  configurations are correct. If the number of available signers on the document is not an exact match to the number of designated signers per contract profile then the automatic process stops.

Users are able to send Nondisclosure Agreements (NDA) through eSignature automation.

How it works

Conga Contracts requires a single DocuSign or user account that can serve as the connection between Conga Contracts and the customer. A single user account needs to be a DocuSign or Adobe Sign Admin user, and is  specifically for Conga Contracts use because the back-end API connection to process packages.

A user should be a generic system user, optimally with a shared internal email account (for example: or as its DocuSign username and have a generic first and last name (for example, First Name: Your Company Last Name: eSignature) when the account is created in DocuSign. As an administrator, you must have access to the shared mailbox to verify account creation with Docusign.

For the eSignature connection, you need one dedicated enterprise admin license from Docusign in order to integrate with Conga Contracts. Conga Contracts Full and Casual Users can then be given permission to set up eSignature packages within the system to send them out for eSignature. It also does not matter who or how many people are e-signing (signatories do not need to be Conga Contracts users), you still need one Docusign license (although you might want more if you want to use them to collect eSignatures outside of Conga Contracts.

  • Was this article helpful?