> 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/launch-e-signature-requests-from-a-salesforce-record.md).
# Launch E-Signature Requests from a Salesforce Record via LWC
In addition to ad-hoc e-signature request building, users can also launch the request process though the Generated Documents Lightning Web Component.
### Request an e-Signature from a Generated Document
Follow these steps to request an e-signature from a PDF generated from a Salesforce record:
From the Salesforce record, generate a document as a PDF using the **S-Docs Generate Documents Lightning Web Component (LWC)** or a configured S-Docs button.
After the PDF is generated, locate it in the **Generated Documents** LWC.
Click the **arrow** next to the generated document to open the dropdown menu of available actions.
Select **Request for e-Signature**.
{% hint style="info" %}
If **Request for e-Signature** does not appear in the dropdown menu, contact your org admin to enable this setting for the **Generated Documents** LWC.
{% endhint %}
Continue through the [**S-Docs e-Signature request builder**](https://help.sdocs.com/sdocs/~/revisions/sNrFnS0Pdr35ElE3TB4w/s-docs-e-signature/create-and-send-signature-requests) experience. The generated PDF is preloaded into the workflow, so you can proceed with configuring recipients, signature fields, and request details as needed.
{% hint style="info" %}
Data write-backs are only supported for this workflow and when the template used to generate the document includes fields that have been configured for write-back functionality.
{% endhint %}
#### Adding Additional Generated S-Docs to a Request (PDF-Upload Format)
When generating a document from an E-Signature prepared PDF-Upload document, you can include additional generated E-Signature prepared PDF-Upload documents stored on the same record using the E-Signature Request Builder workflow.
{% hint style="info" %}
Before you begin, ensure all additional documents have already been generated and are attached to the same record.
{% endhint %}
#### Steps
1. Launch the E-Signature request builder interface by clicking the **Request for E-Signature** option in the Generated Documents LWC.
2. Access the *Documents* tab in the E-Signature Request Builder.
3. Click **Add Document** to open the *Available Documents* panel.
4. Click **Add** next to each document you want to include in the request.
{% hint style="warning" %}
As of the August '26 Minor Release (v13.1), this workflow only supports PDF-Upload templates that include signature input field configurations. Once this workflow os chosen, the end user will NOT have the ability to add static PDFs to the 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 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/sdocs/s-docs-e-signature/launch-e-signature-requests-from-a-salesforce-record.md?ask=&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.
