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
A user should be a generic system user, optimally with a shared internal email account (for