---
title: "ACG Docusign Setup"
canonical: "https://help.agiloft.com/space/HELP/596901951/ACG+Docusign+Setup"
format: markdown
---
This article provides instructions for integrating Docusign with Agiloft CLM using Confidential Authorization Code Grant (ACG) authentication. It guides you through creating a Docusign developer account if you don’t have one, creating the demo Docusign integration app that you’ll promote to production, connecting the demo app to your KB for testing, and then integrating the production app with your KB. The article also includes a recommendation for optimizing your integration.

> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - With ACG authentication, you don’t need to create Docusign User records in your KB in advance. The first time a user creates a Docusign envelope, they're prompted to log in to Docusign and grant Agiloft CLM permission to access their account. When authorization is complete, the system automatically creates a Docusign User record for that user. Make sure all users who will create envelopes have Docusign accounts with permission to access the Docusign REST API.
> ℹ️ - You’ll need to edit the layout for the Docusign Accounts table to add the Integration Method and Secret Key fields. You might need to add the table to your [navigation menu](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714797) so you can access the table setup. To edit the layout, go to Setup Docusign Accounts and go to the Layout tab. Drag Integration Method and Secret Key onto the layout and click Finish to save your changes.

# Creating a Docusign Account

If you don’t already have a Docusign account, you can create a developer account for free. You can use the account for testing during the initial setup. If you already have a Docusign developer account, proceed to [Creating the Docusign Demo App](#docusign_demo).

To set up a developer account:

1. Go to [Docusign for Developers](https://developers.docusign.com/) and click Try for Free.
2. Enter the required details and finish creating the account.

Now you can start setting up the developer or demo app.

# > Macro (anchor)

Creating the Docusign Demo App

To create a Docusign integration application:

1. In your developer account, click the profile icon in the top right and go to My Apps and Keys.
2. On the Apps and Keys screen, click Add App and Integration Key.
3. Give the integration a name, then click Create App. Docusign creates the app.
4. In the app configuration under Integration Type, select Third-party integration key.
5. Leave the Authentication Method set to Authorization Code Grant. Optionally, you can select Require Proof Key for Code Exchange (PKCE).
6. Under Secret Keys, click Add Secret Key. Docusign generates a key.
7. Copy the Secret Key and save it to a safe place where you can access it later. It’s important that you copy the key now because you won’t be able to access it again.
8. Under Additional settings, add the following Redirect URI. Replace the <KB_hostname> placeholder with your KB hostname: `https://<KB_hostname>/extension/ds/connect/authcode/grant`  
For example: `https://example.agiloft.com/extension/ds/connect/authcode/grant`
9. Complete any other optional configuration. Refer to the Docusign’s developer [documentation](https://developers.docusign.com/platform/configure-app/) if needed.
10. Click Save to return to Apps and Keys.
11. On the Apps and Keys screen, copy the Integration Key for the app and the API Account ID and save them in the same place as your Secret Key.

Now you can integrate the demo app with Agiloft to create a testing environment.

# > Macro (anchor)

Integrating the Demo App with Agiloft

To connect the demo app to your KB:

1. Log in to your KB as an administrator.
2. Make sure the layout for the Docusign Accounts table includes the Integration Method and Secret Key fields. To check, go to Setup Docusign Accounts and go to the Layout tab. Confirm the fields are on the layout or add them if they aren’t. You might need to add the table to your [navigation menu](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714797) if you can’t access the table setup.
3. Now, go to **Setup** **> Integration > Docusign Extension** and click Configure.
4. Your KB comes with a Demo (demo.docusign.net) account that you can use to integrate with the demo app. Edit the existing account or click New to create a new account. Note that you can’t have multiple active Docusign accounts if you use ACG authentication with any of them.
5. Give the account a name. If you have multiple accounts listed, make sure to specify a name that differentiates the new account.
6. Select Authorization Code Grant (ACG) as the Integration Method and provide the API Account ID, Integration Key, and Secret Key.
7. Click Save.
8. Click Enable Docusign Connect. If Docusign is fully enabled, you are returned to the account list and the Accept Real-Time Updates? value is set to Yes. You can also confirm your connection by opening the account configuration again and checking that a Connect ID now appears.

Now that Agiloft is connected to your demo app, you can test the integration by [creating and sending envelopes](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/599064639). When you’re ready to promote the demo app to a production account, proceed to [Going Live with Docusign](#going_live).

> Macro (include)

# > Macro (anchor)

Integrating the Production App with Agiloft

Once your app has been verified and promoted to production, follow the steps below to connect your KB to the production account.

1. Log in to your Docusign production account at [https://account.docusign.com/](https://account.docusign.com/), not your developer account.
2. In Admin, go to Apps and Keys under Integrations.
3. Next to the integration key for the app you want to integrate, select **Actions > Edit**.
4. Under Secret Keys, click Add Secret Key. Copy the generated key and save it to a safe place where you can access it later. It’s important that you copy the key now because you won’t be able to access it again.
5. Save and close the app configuration. On the Apps and Keys screen, copy the API Account ID and save it to the same location as the secret key.
6. Now log in to your KB.
7. Go to **Setup > Integration > Docusign Extension** and click Configure.
8. Edit the account configuration you used to connect to the demo app.
9. Click Disable Docusign Connect.
10. At the top of the screen, edit the Account Name if necessary.
11. Next, click** **Change Server, select the Account Base server for the production app, and click Set Server.
12. Change the API Account ID and Secret Key to the values for the production app.
13. Save the record and then click Enable Docusign Connect. If Docusign is fully enabled, you are returned to the account list and the Accept Real-Time Updates? value is set to Yes. You can also confirm your connection by opening the account configuration again and checking that a Connect ID now appears.

Now that your production account is integrated with Agiloft, you can test it by creating a new contract and sending it out for signature. See [Recommended Optional Setup](#recommended_setup) for a recommendation to optimize your integration.

# > Macro (anchor)

Recommended Optional Setup

To optimize your Docusign integration, you can customize the Create Docusign Envelopes action.

> Macro (include)

#### Related articles

> Macro (contentbylabel)