There are many instances where multiple people need to sign a single document. Fortunately, S-Sign provides this capability! This article will explain how to configure S-Sign for multiple signers in Salesforce Lightning Experience.
Start by creating a new S-Docs template. We'll call our example template "Loan Agreement." If you are working with a pre-existing S-Sign enabled template, you can skip this step.
Click Save, and then open the S-Docs template in the S-Docs Template Editor.
To enable S-Sign for this template, navigate to the Advanced Options tab and check the Enable S-Sign checkbox. The S-Sign panel will appear on the left, and allow you to edit the options associated with this S-Sign template.
Signer profiles allow you to define the email address of each signer, the order in which they will receive and sign the document, and whether or not each one receives a copy of the audit record after the document has been finalized. To learn more about these settings, please visit our S-Sign Template Settings article.
The Signer profiles menu is located in the S-Sign panel to the left of the template editor. By default, S-Sign provides you with two profiles: Signer 1 and Signer 2. In our example, we have renamed our profiles to "Borrower" and "Lender." You can create additional profiles here as well, though we'll just stick with two profiles in this example.
Next, we will associate emails to the two profiles. You can either type in each signer's email address directly, or use merge fields to dynamically populate the email address field based on the record that this document is generated from.
Previously, we created custom fields on our template's base object (Contract) to determine the email addresses that will be assigned to each profile. Our two custom fields are Lender email and Borrower email. To pull data from these fields, first click Insert Field in the template editor.
This will show all available fields to pull data from on the contract object. Search for your custom fields and click Copy to Clipboard.
You can then paste them into the "Email Address" field in the signer profile menu. As we mentioned before, you can also specify the order in which the users will receive the E-Signature request; in this example, the Borrower will receive the request first since the Borrower's Signing Order is "1," and the Lender will receive the request after the Borrower has signed the document since the Lender's Signer Order is "2."
The next step is associating S-Sign fields to the appropriate signer profiles. Click over to the S-Sign Fields tab in the S-Sign settings menu. S-Sign provides you with a single S-Sign Field by default. In this example, we created 3 S-Sign fields for each signer: signature, checkbox, and text (6 fields total).
We can then edit, copy, and paste our S-Sign Fields into the template body:
Each signer will only be able to interact with the fields that are assigned to their profile.
After saving your template, users can generate documents using this template and an S-Sign-enabled HTML email template and then send those documents for e-signature. The email page will inform the end user of the routing logic that will be used in the emailing:
Signer 1 (the "Borrower" in our example) will be emailed the document first. When they click the S-Sign link in the email, they will be asked to verify their identity (if enabled for that template) and will be informed of the email routing logic.
Once Signer 1 has verified their identity (if required), they will be able to provide values for their assigned S-Sign Fields (the checkbox, text field, and signature), but NOT for the S-Sign Fields assigned to Signer 2 (the "Lender" in our example). Signer 1 can use the Previous and Next buttons to navigate through their assigned inputs.
Here is an example of input provided by Signer 1 (the "Borrower"):
Once Signer 1 (the "Borrower") submits their responses, the document will be emailed to Signer 2 (the "Lender"), and Signer 1 (the "Borrower") will see the following screen:
When Signer 2 (the "Lender") opens the e-signature request, they will see previous signer's responses merged into the document.
Signer 2 (the "Lender") can then provide their input:
Signer 2 (the "Lender") will see the following page once they have submitted the signed document, and the signed document will be sent to Signer 1 (the "Borrower"), Signer 2 (the "Lender"), and the Salesforce user who originally sent the e-signature request.
The final signed document from our example will appear as follows:
By scrolling down, the audit trail for the document can also be viewed.
That's it! You are now ready to send e-signature requests that require multiple signers.