Start by creating a new S-Docs template. We'll call our example template "Loan Agreement":

Open the S-Docs template in the S-Docs Template Editor. In the Advanced Options tab, set the "E-Sign Vendor" field to S-Sign. An interface will appear that will allow you to edit the options associated with this S-Sign template:

We'll start by modifying the signer profiles. 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. In our two profiles, we have specified merge fields on our template's base object (Contract) to determine the email addresses that will be assigned to each profile (you can copy merge field using the "Insert Field" button in the S-Docs Template Editor). 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".

We can then create S-Sign Fields and assign them to these profiles. S-Sign provides you with a single S-Sign Field by default. In this example, we created 6 S-Sign Fields:

  • A Signature field assigned to the Borrower profile
  • A Signature field assigned to the Lender profile
  • A Checkbox field assigned to the Borrower profile
  • A Checkbox field assigned to the Lender profile
  • A Text field assigned to the Borrower profile
  • A Text field assigned to the Lender profile

We can then edit copy and paste our S-Sign Fields into the template body:

After making these changes, we save our template. A user can then 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). 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: