> 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/e-signature-inputs.md).

# E-Signature Inputs

{% columns %}
{% column valign="middle" %}

<figure><img src="/files/cabHDh2qrGXfmDh6dqe4" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

#### Signature

Allows the signer to draw or type their full signature to confirm authorization or agreement.

#### Initials

Captures the signer’s initials, commonly used to acknowledge specific sections or individual clauses within a document.

#### Text

Provides a freeform text field for entering custom information such as names, titles, comments, or identifiers.

#### Date

Captures a date value, typically used to record when a document was signed or approved. Supports various date formatting options.
{% endcolumn %}
{% endcolumns %}

#### Number

Restricts input and validates numeric values only, useful for IDs, quantities, percentages, or other number-based entries.

#### Email

Captures a valid email address and can enforce standard email formatting requirements.

#### Phone

Captures a phone number in a standardized format for contact or verification purposes.

#### Checkbox

Allows the signer to confirm or acknowledge a statement by selecting or clearing a checkbox.

#### Picklist

Provides a predefined list of selectable options, ensuring consistent and standardized responses. Options can be defined manually or driven by picklist field data from a Salesforce record.

### Configuring Input Fields to Write Data Back to Records

Input fields include the ability to define a location in which signer supplied data can be written back to the Salesforce generating record.

{% hint style="info" %}
Signature and Initials input fields do no support write-backs to records. Data write-backs only apply updates to and from [**e-signature requests that are initiated from a specific record**.](https://help.sdocs.com/sdocs/~/revisions/tQryHJcKs5a9X6UOG4oU/s-docs-e-signature/launch-e-signature-requests-from-a-salesforce-record)
{% endhint %}

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

To configure a data write-back:

Click on the input field in the template body to lauch the field configuration menu.

Navigate to the **Assignment** section.

Select the field from the drop-down menu that will receive the signer-provied information.

Upon successful submission and processing of the signature request, the provided information will update the appropriate record automatically.


---

# 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/e-signature-inputs.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.
