After you complete the negotiation process with the customer, you can send the finalized agreement document to the customer for gathering signatures. When the agreement is ready to execute, you can collect the required internal and external signatures. Depending on your organization's requirements, you can send the agreement document for a manual signature to your customer or if a third-party application, such as Echosign or DocuSign is installed in your org, you can send the agreement document for an electronic signature. Once you receive the manually signed documents from the customer, you can upload the signed documents to finalize the agreement. Documents in the review are not available to send for signatures or eSignatures. 

User Permissions Needed
To send a document for signature:Agreement: Edit.


 Before sending the agreement document for signature, you must ensure that a final version of the agreement document is present in the Notes & Attachments related list.



You cannot send a document with protection for signatures if your organization has set up High-Assurance Session Security at a user profile level. As a result of the security, the sessions cannot be generated in asynchronous calls.

To Send an Agreement for Manual Signature

  1. From the Agreement detail page, click the Send for Signature button.
  2. From the Attachments section, select the file to send for signature and click Next
  3. (Optional) Select files to attach to the review email from Parent, Child, or other agreement records related to the current agreement. 
    1. Select the type of agreement to show attachments from. 
    2. Select any attachments from the list displayed under "Attachments" to add to the review email.

      In Version Aware agreements, it is recommended to select a document associated with document version for agreement clauses to be marked as Final.

    3. Repeat steps a – b for additional agreement types.
    4. Click Next when you are finished.

    The Show Attachments From page is only shown if the current agreement has related records.

  4. (Optional) Choose the form of document protection to be applied to any documents selected as attachments in the previous steps.


    The Apply Document Protection page is only shown if Agreement Document Protection rules for "Send to Other Party for Review" are specified and properties for document protection are enabled. For more information, see Use Case for Setting Up Agreement Document Protection and Admin Entries.

  5. (Optional) Select an appropriate template for your agreement document and click Next.

    Important Notes on Email Template Selection

    • A default email template is usually configured by your administrator (using an Admin property) for the Send for Signature action. Check with your administrator if you are unsure.
    • If no Email Template is selected and no default email template has been configured (using the above properties), the Email Template "Email Template For Review Signature" is used. In most cases, this template not configured as "Available for Use" and must be manually set to true or an error will occur. In the case of a new installation of the package (non-upgrade), this Email Template is automatically configured as "Available for Use."
    • You cannot return to the Select Email Template page after you click Next. If you decide you want to use a different email template after this point, you will have to cancel the Send for Signature and start over from the agreement record.
  6. In the To field, enter the name of the contact you want to send the document to. 


    At least one recipient must be specified in the To field. If the email IDs or contacts specified in the To or Additional To fields are invalid, when the APTS_EnableValidationForEmailWithoutUserContact property is set to true, an error is displayed.

  7. Enter or use the Lookup icon to add recipients to the Additional ToCc or Bcc fields.


    If there are many contacts (for example, more than one million), you can launch a custom pop-up page where you can quickly search and select contacts for the Additional To, Cc, and Bcc fields.

    1. Click the Lookup icon next to the Additional To field to launch the Email Address Lookup window.
    2. Search for contacts and add them to the Additional To RecipientsCC Recipients, and BCC Recipients lists.
    3. Click Save.

    You must set the admin setting APTS_EnableCustomEmailAddressLookup to True-only then is the custom pop-up page is displayed; otherwise, the standard Salesforce pop-up page is displayed. At least one recipient must be specified in the Additional To field.

  8. Type a mandatory Subject and Body for your email and click Send
    This activity is logged in the Activity History. The Status Category and Status of the agreement record are updated to In Signature and Other Party Signature respectively.

According to the Email Attachments configuration, when you send documents for review, recipients can view the documents as links or HTML attachments. For more information, see Salesforce Documentation.

After the agreement document is signed, all the clauses are marked as Final in the Agreement Clauses section. In version aware agreement, Document Type of the signed document is updated as the Executed Document.  An executed document is a finalized version of an agreement that is ready for activation.


The Admin Property APTS_DefaultEmailContactName is required to create an "Email: Subject" entry on the Agreement record Activity History Related List after the email is sent. If the property is not defined or is invalid, details are not recorded in the Activity History. After the customer signs the agreement document, you can activate the agreement.

To Send an Agreement for Electronic Signature

  • You must have sent a generated Agreement document to the customer for review.
  • You must ensure that the Status Category for the Agreement record is In Authoring.

From the Agreement detail page, click the eSignature button. This action takes you to the EchoSign or Docusign wizard. For more information on EchoSign, see Adobe Sign Services documentation. For more information on DocuSign, see DocuSign Services documentation.

The following conditions apply when you send documents in Version Aware agreement for eSignatures in DocuSign:

  • The Status Category changes to In Signatures and the Status changes to Other Party Signatures for your agreement record.
  • The signed agreement documents are stored in the Document Version related list.
  • All the agreement clauses are marked as Final.
  • The Document Type is updated to Executed Document.


After an agreement document is signed, all the smart clauses are marked as Final in the Agreement Clauses section. 

The following conditions apply when you send documents in Version Aware agreement for eSignatures in EchoSign:

  • You can send generated, regenerated, supporting, imported offline, created offline, or manually uploaded documents.
  • You can select any document from Files or Notes and Attachments. You can also select the latest document version from the Document Version related list.
  • The Document Type of the signed document is updated as the Executed Document.
  • The intermediate signed documents from EchoSign are available in Contract Management as a major document version with name as Intermediate Signed Document in the Document Version related list. In version aware agreement, the Document Type of the document is updated to Intermediate Document.