S-Sign User Guide – Salesforce Lightning Experience

This article provides a comprehensive overview of creating and sending an e-signature request with S-Sign in Salesforce Lightning Experience, as well as explains what happens behind the scenes. To view this article for Salesforce Classic, click here.

Tutorial Video

Sending the E-Signature Request

Sending an E-Signature request with S-Sign is as simple as generating a document and sending an email. Once you have created an HTML E-Signature request template and a signable PDF template, navigate to a Salesforce record and click the S-Docs button. If you don't see the S-Docs button, you either need to add it to your page layout (if you're viewing select standard objects) or you need to create the button and add it to your page layout (if you're viewing a custom object).

Next, select your HTML E-Signature request template and your signable PDF template. You can tell which templates are S-Sign enabled by the S-Sign logo that appears next to the template names. Click Next Step to generate documents with these templates.

S-Docs will then recognize that you have generated an E-Signature document and offer a Send Documents for Electronic Signature button. Click this button to email the E-Signature document. Click here to learn about using S-Sign in person.

If you didn't specify the email of the signer in the template editor, you will be prompted to enter their email now. If your template requires multiple signers, you will be able to enter the email address of each signer here.

Upon clicking Next Step, you will be brought to the the email page. Here, you have the option to edit the usual email fields (To, CC, BCC, Subject).

Note that you also have the option to edit the body of the email.

Note that the PDF we generated is not included on this email as an attachment; this is because the email contains a link to an interactive webpage where the user can view and sign that PDF (this is the code you inserted into your HTML template when you created it). Click Send to send the document for E-Signature.

Note: Additional attachments (non-S-Sign documents or pre-generated documents) are not supported with S-Sign emails at this time.

What the Signer Will See

The recipient then receives the email that you created with your HTML template:

When the recipient clicks View and Sign, they will be prompted to verify their identity by entering a code and consenting to do business electronically.

They will then be taken to the signable document.

From here, the recipient can decline to sign, or they can sign the document by clicking Sign Here, which will bring up the signature pad.

The recipient can then type their name, draw a signature, and submit their information.

Once the recipient clicks Submit Signature, their signature is merged into the document, and both you and the recipient receive a confirmation email containing the signed document. The recipient is then  redirected to view the signed version of the document. The signed version of the document includes the signer’s name, their signature image, and the date and time at which they signed the document. Additionally, the audit trail for the document appears as a new page at the end.

Note: To learn how to customize aspects of an S-Sign request, such as the size of the signature image and who receives the audit record, please visit the S-Sign Templates Settings documentation.

Note: You can send multiple documents in a single e-signature request. Click here to learn how to do this.

Behind the Scenes - Before Signature

What happened in Salesforce while all of this was going on? Let’s take a step back in time to way before our recipient has signed the document. Immediately after you clicked Send Documents for Electronic Signature, an S-Sign Envelope record was created, which can be viewed under the Related tab on the object record that you created the e-signature request for.

Click on the blue link to view the S-Sign Envelope record. Under the Details tab, you can [1] view and track the sign status of your request; since the recipient hasn't opened the email yet, it's status is "Created." This will change to "Viewed" when the recipient opens the document, and "Signed" once they sign it. You can also [2] view the template ID used for the email, [3] the number of documents that need to be signed, and [4] the HTML email page itself.

Under the Related tab, you'll be able to see S-Sign Envelope Document records, one for each signable PDF that was included in our E-Signature request (in this case, only 1). You can [1] click on the PDF icon to view the document that is going to be signed, or [2] click on the Envelope Doc Number to view the document record. We'll click this number now.

On the S-Sign Envelope Document record, you'll be able to see more details. You can [1] view the Sign Status again, as well as [2] the current signer identity (this is useful when your documents require multiple signatures). Once the document has been signed, you'll be able to [3] view the finished product on this page, as well as [4] the original document before signature. Finally, you can [5] view the S-Sign request URL, as well as the signature image by itself.

Under the Related tab, only the original document is visible.

Behind the Scenes - After Signature

Now let’s take a step forward in time to when our recipient has signed the document. Again, head to the object record you generated the e-signature request from, and click on the S-Sign Request link under S-Sign Envelopes.

At this point, the S-Sign Envelope's status has been updated to "Completed."

Under the Related tab, a link has appeared to view the signed document.

When you click on the Envelope Doc Number, the Related tab now contains files for the document audit trail, the raw signature file, the signed document, and the original document.

The signed document file will also appear in the Notes & Attachments related list on the contact record.

That's all there is to it!

Tags: , , , ,

Was this helpful?