> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/define-signer-profile-and-routing/e-signature-requests-multiple-signers.md).

# E-Signature Requests: Multiple Signers

Sending documents to multiple signers allows you to automate complex signing workflows, such as "Borrower" and "Lender" agreements, by defining specific roles and orders for each recipient.

***

### 🛠️ Step 1: Template Configuration

To begin, you must prepare your S-Docs template for electronic signatures.

* Enable S-Sign: Navigate to the Advanced Options tab in the S-Docs Template Editor and check Enable S-Sign.
* Access the S-Sign Panel: Once enabled, a new panel appears on the left side of the editor to manage signing logic.

### 👤 Step 2: Creating Signer Profiles

Signer profiles define *who* signs and *when* they sign.

* Default Profiles: S-Sign provides "Signer 1" and "Signer 2" by default.
* Customization: You can rename these (e.g., "Client," "Manager") and add additional profiles as needed.
* Assigning Emails:
  * Static: Type the email address directly.
  * Dynamic: Use Merge Fields to pull email addresses from Salesforce records (e.g., `{{!Contact.Email}}`).
* Signing Order: Assign a numerical value (1, 2, 3...) to determine the sequence. Signer 2 will only receive the document after Signer 1 has completed their portion.

### ✍️ Step 3: Mapping Fields to Signers

Each signature, checkbox, or text field must be "owned" by a specific profile.

* S-Sign Fields Tab: Located in the S-Sign settings menu.
* Field Assignment: When you create or edit a field (Signature, Date, Checkbox), you must select which Signer Profile it belongs to.
* Permissions: Signers can only see and interact with fields assigned to them. They cannot edit fields assigned to other signers.

***

## 📧 The Signing Experience: Step-by-Step

Understanding the workflow from the recipient's perspective is key to ensuring a smooth signing process.

#### 1. Initial Email Delivery

* Signer 1 receives an email with a secure link.
* The email page informs the user of the routing logic (e.g., "Once you sign, this will be sent to the Lender").

#### 2. Identity Verification

* If enabled, signers may be asked to verify their identity (via email code or SMS) before accessing the document.

#### 3. Interactive Signing

* Navigation: Signers use Previous and Next buttons to jump between their assigned fields.
* Validation: The system ensures all "Required" fields (like the Signature) are completed before allowing submission.

#### 4. Progressing the Workflow

* Once Signer 1 clicks Submit, S-Sign automatically triggers the email to Signer 2.
* Finalization: After the last signer completes the document, all parties receive an email with the fully executed PDF and a complete Audit Record.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/define-signer-profile-and-routing/e-signature-requests-multiple-signers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
