The DocuSign account used for the Conga Contract integration must not have SSO enabled. It must allow username and password authentication.
Self Service DocuSign settings management
You can manage your DocuSign integration settings like usernames, passwords and other security features in the Admin section of Contracts Before you begin, you need your DocuSign API Username and Account ID. To obtain your DocuSign API Username and Account ID, take the following steps:
- Log in to your DocuSign account
- Click on Profile
- Click Admin
- Under Integration on the left, click on API and Keys
- Under My Account Information, you will need the API Username and the API Account ID
- Next, return to Conga Contracts to complete the integration setup.
- Under Administration, click on System Settings
- Enter the API Account ID under DocuSign Account Id
- Enter the name of your DocuSign Account name under DocuSign Account Name
- Enter the API Username under DocuSign Username
- Enter your DocuSign password under DocuSign Password
- Click Update
The values relate to the fields and 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 Enterprise Admin DocuSign or user account to serve as the connection between Conga Contracts and the customer. This account needs to be a DocuSign Admin user, and dedicated specifically for Conga Contracts use because of the back-end API connection required to process packages.
You can assign DocuSign users with DS Signer permissions instead of only assigning users with DS Admin permissions, but you will not have access to the user's API Username because DS Signer permissions do not have access in DocuSign to see API Usernames.
It's strongly recommend to create a generic system user for this account, optimally with a shared internal email account (for example: firstname.lastname@example.org) as its DocuSign username, and to use 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.
Conga Contracts Full and Casual Users are given permission to set up eSignature packages within the system to send them out for eSignature. It does not matter who or how many people are e-signing (signatories do not need to be Conga Contracts users), only one DocuSign license is required.