---
title: "Manage Documents with Adobe Sign"
canonical: "https://help.agiloft.com/space/HELP/599294008/Manage+Documents+with+Adobe+Sign"
format: markdown
---
Document signing is typically integrated into a workflow between signing parties as part of the contract management process. Using Adobe Sign with Agiloft CLM allows you to send documents to different parties to sign and then track and manage those documents in your KB. The documents to be signed are either uploaded into a field in the relevant record, directly added in the Attachments table, or generated from document templates. For more information on using document templates with Adobe Sign, see [Create Document Templates with Adobe Sign Tags](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/597590092). 

The signing process can be initiated directly from a record, and you can select one or several documents to be sent for signing at once. The documents you can select are determined by the To Be eSigned field in the Attachment record for the document. An action button with an Adobe Sign action allows you to begin the signing process.

![Signatures tab in a Contract record showing To Be eSigned and Create Adobe Sign Agreement](media://7224421d-bfdb-47e6-a206-130b99f156a9)

Adobe Sign is integrated with the Contracts table by default. For information about integrating Adobe Sign with other tables, see [Adobe Sign Actions in Other Tables](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/599195885).

> ℹ️ **Useful to Know**
> ℹ️ 
> ℹ️ - Adobe Sign uses the term "agreement," which is synonymous with "envelope" in older version of Agiloft CLM. Adobe Sign documents are sent in the form of agreements, which must be purchased directly from Adobe.
> ℹ️ - Adobe imposes a size limit per agreement. If the total file size of the agreement exceeds that, it fails on sending. For best results, limit your file size to 5 MB or less.

# Configure Signing Order and Signature Flow

Signing order and signature flow are two approaches for determining how Adobe processes the document for signing between recipients. Signing order allows you to define the exact order that recipients receive the document to sign. Signature flow provides a more general approach for defining the recipient order and is only used in cases where the signing order hasn't been defined. We strongly recommend that you always use signing order because it is more reliable and offers more control over the recipient order. However, in both cases, the user can confirm the recipient order by previewing the agreement before sending it.

## Signing Order

To configure the default signing order for a document:

1. Click Setup [Table] and then click the Actions tab. By default, Adobe Sign is integrated in the Contracts table.
2. Go to the Actions tab and edit the ext:Create Adobe Sign Agreement action. Adobe Sign must be integrated into the table for this action to appear.
3. Click the Recipients tab.
4. Define the total number of recipients, as well as each recipient's signing order, role, field in the record that defines the signer, and optional message.
  The maximum number of recipients is 9, and recipients can have one [Adobe Sign role](https://helpx.adobe.com/sign/using/set-up-signer-approver-roles.html). Delegate roles are available for Enterprise accounts, and in order to use them, you must log in to Adobe Sign as an administrator, go to Account > Account Settings > Send Settings > Allowed Recipient Roles, and select the "Allow senders to mark some recipients as delegators" checkbox. Delegates receive the document, and can review it, but they can't interact with it otherwise; instead, they must enter the email address for the person they are delegating to, and the document is sent to that address to complete the role's responsibilities. Delegates can't enter the email address for someone who is already a party to the current agreement.

> 📝 You can also set a recipient's signing order if you add a recipient when you create an agreement. For more information on creating agreements, see <u>[Create Adobe Sign Agreements](https://agiloft-public.atlassian.net/wiki/spaces/hdrafts/pages/44009501)</u>.

5. Click Save.

## Signature Flow

We strongly recommend that you always use signing order because it is more reliable and offers more control over the recipient order. However, if you need to use Signature Flow, use the steps below to configure the default signature flow for a document.

You can also set the signature flow when you create an agreement. For more information on creating agreements, see [Create Adobe Sign Agreements](#create).

1. Click Setup [Table] and then click the Actions tab. By default, Adobe Sign is integrated in the Contracts table.
2. Go to the Actions tab and edit the ext:Create Adobe Sign Agreement action. Adobe Sign must be integrated into the table for this action to appear.
3. On the Adobe Sign Action tab, use the Signature Flow field to choose a signature flow option. If a signing order has been defined, any choice here is ignored.
  These options are available:
  - **Sequential: **Follows the signing order defined in the recipient list.
  - **Sender signs only/last/first/not required**: Forces the sender to sign in a different order from the recipients. To use these options, you must add the sender as a recipient in the expected location.
  - **Parallel:** Sends the document for signing simultaneously to both the sender and recipients.
4. Click Save.

# > Macro (anchor)

Create Adobe Sign Agreements

Documents used with Adobe Sign are sent using agreements. An agreement acts as a container that holds the document, recipient information, signing order, and other processing details. You can create new agreements in the Adobe Sign Agreements table or, more typically, in another table where Adobe Sign has been integrated. For instance, the Contracts table in the out-of-the-box knowledgebase has a Signature tab with a Create Adobe Sign Agreement action button.

> ✅ In older KBs, you might see "envelope" used in place of "agreement." The functionality is the same.

To create an Adobe Sign agreement from a table with Adobe Sign integration:

1. Open a record and go to the Signature tab.
2. If the table has fields for selecting the documents to be signed and the recipients, populate them with the desired files and people. Select the documents in the order you want to show them, if possible.
3. Click Create Adobe Sign Agreement.
4. Edit or enter an email subject.
5. Optionally, add comma-separated email addresses to the Additional Email field to CC additional users. Any email addresses included in this way receive a copy of the document when the agreement is sent, as well as a copy of the completed document when all signatures have been received.
6. If you didn't define the documents and recipients in step 1, add them using the fields in the agreement.
  - Attach the documents in the order you want to present them to the recipients.
  - Recipients do not have to be added as an Adobe Sign user before they can sign agreements. In the Recipient record, enter their position in the signing order, full name, email address, and role. You can also use the Authentication Method field to use a single sign-on method, a password, or have no form of authentication, if you don't want to automatically authenticate users from within the document.
7. Choose a reminder frequency. This determines how often the recipient is reminded until they sign the document.
8. Set a deadline. After the deadline is reached, the agreement expires and the documents can no longer be signed.
9. Click Preview/Send to preview the agreement and make sure everything looks right before you send it.
10. In the Preview page, confirm the email addresses and signing order. Click and drag recipients to change the order, or click the address or signing position numeral to edit them. You can also use the toggle to switch between sequential signing and simultaneous signing.
11. Review the message that will be sent along with the documents and make any necessary adjustments.
12. Review all the attached documents, and their order. You can drag and drop to change the order of documents, and you can upload additional files if necessary. However, files added here are not tracked in the Agiloft CLM agreement record.
13. If desired, you can use the Options section to set a password, override the reminder frequency you set in step 7, or set another language for the recipients.
14. When everything is correct, click Send.

## Signing Process

The first recipient specified in the signing order or signature flow receives a notification by email that contains the document to be signed.

![image](media://0bc1cbca-d18a-47fa-a7c8-90833dddd442)

Adobe Sign automatically adds signature blocks to the document so that the recipient can insert their signature. Recipients do not need to have an Adobe Sign account to use their email address to sign the document. For more information, Adobe’s [documentation](https://helpx.adobe.com/sign/using/signing/sign-agreements-sent-to-user.html).

Recipients and senders are notified by email during the signing process. Recipients receive a second notification after they sign a document. The sender receives a notification when a document is sent for signing, when a recipient signs a document, and when all recipients have signed a document.

### Tracking the Signing Process

To track the progress of a document and manage the audit trail, open the record in the Adobe Sign Agreements table and click the History tab. The statuses of the agreement workflow are updated automatically by Adobe and maintained in the Adobe Sign Statuses table. For more information, see [Adobe Sign Tables Overview](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434009).

# Combine Documents

By default, Agiloft CLM is configured to merge multiple documents and any certification into a single PDF after signing. If you have Adobe Sign set up to keep documents separated and want them to remain separate in your KB, follow the steps below to change a setting in the Adobe Sign Agreements table.

1. Find the Adobe Sign Agreements table and go to **Setup Adobe Sign Agreements**.
2. Go to the Fields tab.
3. Edit the Receive Combined Document field and go to the Options tab.
4. Under Select the default value to display, select No in the “Choose from the list” drop-down. This changes the default value to No so signed documents aren’t automatically combined.
5. Click Finish to save the change.
6. If the Receive Combined Document field isn’t shown in Adobe Sign Agreement records and you want to display it, follow the steps below to change the record layout. In newer KBs, the field is included on the History tab by default:
  1. Go to the Layout tab.
  2. Decide where in the layout you want to add the field, then drag and drop Receive Combined Document onto the layout.
  3. Click Finish to save the change.

Your KB is now configured to keep any new multiple document agreements separate after they’re signed.

#### Related articles

> Macro (contentbylabel)