> 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/configuring-the-request-e-signature-action-for-salesforce-record-pages.md).

# Configuring the Request E-Signature Action for Salesforce Record Pages

Adding a custom E-Signature action to a Salesforce record page enables end users to send on-the-fly E-Signature requests directly from their daily workflow, removing friction in day-to-day processes and accelerating desired business outcomes.

#### Step 1: Create the Custom Action

1. Click the gear icon in the upper right of the Salesforce interface and select *Setup*.
2. Select *Object Manager*.
3. Search for and select the base object where you want to implement the request for E-Signature action (e.g.: *Opportunity*)
4. Select *Buttons, Links, & Actions* from the sidebar menu.
5. Click **New Action**.

#### Step 2: Configure the Action

1. Select *Lightning Web Component* in the *Action Type* field.
2. Select *SDOC:requestSignatureFromRecord* in the *Lightning Component* field.
3. Enter a clear name in the *Label* field (such as "Request e-Signature") so end users can instantly recognize the action.
4. Click **Save**.

<figure><img src="https://1548664070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWKNnJmhJBQwhdk5WBFsi%2Fuploads%2FHuud19dpE9JMgOvhqMxq%2FNew%20Action%20SS.png?alt=media&amp;token=72d022d5-127b-4629-a1c7-0d283604ded8" alt=""><figcaption><p><em>Example of a fully configrued action.</em></p></figcaption></figure>

#### Step 3: Add the Action to the Page Layout

1. From the same base object in *Object Manager*, click **Page Layouts**.
2. Select the specific page layout you want to update (e.g.: Opportunity Layout).
3. Click **Mobile & Lightning Actions** in the layout palette.
4. Drag your newly created action into the *Salesforce Mobile and Lightning Experience Actions* section.
5. Click **Save**.

{% hint style="info" %}
The action button wil now be available to end users on every record of that object. Clicking the action button launches the E-Signature Request Builder, which automatically logs request status details directly back to that record.
{% 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/configuring-the-request-e-signature-action-for-salesforce-record-pages.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.