> 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/sdocs/s-docs-e-signature/create-and-send-signature-requests.md).

# Create and Send Signature Requests

{% hint style="info" %}
S-Docs e-Signature functionality is available starting with the Spring '26 (S-Docs v12.0) release.
{% endhint %}

### Preparing e-Signature Requests

This feature allows you to upload previously generated PDF documents for use in S-Docs e-Signature requests.

With the S-Docs app launched in Salesforce, access the e-Signature workflow by selecting **S-Docs E-Signature** from the lightning dropdown menu.

<figure><img src="/files/OMt0L4pzLlFcHOQjEKkx" alt=""><figcaption></figcaption></figure>

Click the **+Add** button to initiate the e-Signature Request creation workflow.

{% hint style="info" %}
The S-Docs e-Signature request builder workflow can also be initiated straight from a Salesforce record by selecting the [**Request e-Signature** LWC option for a PDF listed in the Generated Documents LWC.](https://help.sdocs.com/sdocs/~/revisions/tQryHJcKs5a9X6UOG4oU/s-docs-e-signature/launch-e-signature-requests-from-a-salesforce-record)
{% endhint %}

### The e-Signature Request Workflow

The request builder interface includes a horizontal tabbed menu labeled **Documents**, **Signers**, **Fields & Data** and **Review & Send**. To customize your request, simply complete each step in order.

<figure><img src="/files/NEjk2hEcreiataRpI0Io" alt=""><figcaption></figcaption></figure>

#### Documents

Add documents for e-Signature by clicking **Add Document** and select from the file menu, or simply drag and drop PDFs right to the indicated area. If you initiated the e-signature request workflow from a Salesforce record via the S-Docs Lightning Web Component (Generated Documents LWC), then that PDF will already be loaded into the Documents interface.

{% hint style="info" %}
If the request includes multiple documents uploaded, the order in which documents appear in this list are the order in which they will be presented to the recipient(s).
{% endhint %}

To change their order, simply drag and drop your documents (using the vertical grip dots icon to the left of each document). You can also delete any documents you no longer need to send.

#### Signers

Next, define recipients. Enter the recipient(s) name and email address, and enable/disable the one-time password (OTP) setting for each signer.

{% hint style="info" %}
Multiple recipient requests are set to non-sequential signing by default. If the request is required to follow a specific signing order, enable the option labeled **This document must be signed in the order above.**

If this option is enabled, the order in which the signers appear in this list are the order in which the the recipient(s) will receive the request.
{% endhint %}

To change the signer order, simply drag and drop the signers (using the vertical grip dots icon to the left of each document). You can also delete any signers you no longer need to send to.

#### Fields & Data

Add signer input fields to the desired locations on the uploaded document(s). The signer input fields are configurable and will be active to the assigned signer profile for the signature request. Fields can also be configured to write inpout back to the request's associated Salesforce record.

<figure><img src="/files/AUq6coSTlHVduFGf6x5P" alt=""><figcaption></figcaption></figure>

#### Review & Send

Create the email that sends to the defined recipients with your e-Signature-ready documents.

* **Subject Line:** Write something short, simple, and clear so that your recipients know what the email is about.
* **CC Recipients:** Add more recipients under “CC Recipients.” Enter emails and tap the **tab key** after each email to add more.
* **Email Body:** The email body section will automatically populate with a default email template; edit it as you see fit. Give your email a good proofread and add any critical details.

<figure><img src="/files/gIdmx63DGQcRgf5rL7aP" alt=""><figcaption></figcaption></figure>

When your email is finalized, click **Request Signature** in the upper right corner or below the email message panel. A pop-up will appear confirming that the email was sent.

{% hint style="info" %}
Return to the **e-Signatures dashboard** to view all and track progress on any e-Signature request.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sdocs.com/sdocs/s-docs-e-signature/create-and-send-signature-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
