Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

DocuSign Self Service implementation

Warning:

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 will need to generate an App Password from within your Docusign account. To set up the Docusign integration, take the following steps:

  1. Open your Docusign Account Profile Page.
  2. Select Privacy & Security in the left navigation menu, then confirm your credentials.
  3. Find the App Passwords row in the Additional Security section, then select GENERATE APP PASSWORD.
  4. In the Generate App Password dialog box, choose a custom name for the App Password, then select GENERATE APP PASSWORD.
  5. Copy the generated App Password and record it in a secure place. It will only be displayed once. Select GOT IT to return to your profile page.
  6. Next, return to Conga Contracts to complete the integration setup.
  7. Under Administration, click System Settings.
  8. Go to Integration > Settings.
  9. Set the Docusign Base URI (typically this is https://www.docusign.net/api/3.0/api.asmx)
  10. Set the App Password (the value you stored from Step 5).
  11. Click Update.

The values relate to the fields and, with the exception of Docusign App 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.

Note:

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: legal@companyname.com) 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.