> 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.md).

# S-Docs e-Signature

- [Configure S-Docs e-Signature and Global Settings](https://help.sdocs.com/sdocs/s-docs-e-signature/configure-s-docs-e-signature-and-global-settings.md)
- [Create and Send Signature Requests](https://help.sdocs.com/sdocs/s-docs-e-signature/create-and-send-signature-requests.md): Learn how to prepare a document for e-Signature and send it to your desired recipients.
- [E-Signature Inputs](https://help.sdocs.com/sdocs/s-docs-e-signature/e-signature-inputs.md): Exploring the library of inputs and functionality available for S-Docs e-Signature requests.
- [Launch E-Signature Requests from a Salesforce Record via LWC](https://help.sdocs.com/sdocs/s-docs-e-signature/launch-e-signature-requests-from-a-salesforce-record.md): In addition to ad-hoc e-signature request building, users can also launch the request process though the Generated Documents Lightning Web Component.
- [Configuring the Request E-Signature Action for Salesforce Record Pages](https://help.sdocs.com/sdocs/s-docs-e-signature/configuring-the-request-e-signature-action-for-salesforce-record-pages.md)


---

# 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.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.