> 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/configure-s-docs-e-signature-and-global-settings.md).

# Configure S-Docs e-Signature and Global Settings

S-Docs has introduced new global configuration settings designed specifically to simplify configuration and automate processes within [enhanced template editing](/sdocs/enhanced-template-editor/configuring-settings-for-enhanced-templates.md) and e-Signature workflows. These options allow administrators to establish organization-wide defaults for document formatting, naming conventions, file handling, and signing workflows.

{% hint style="info" %}
These settings are located within the *S-Docs Settings* page. They are entirely separate from the classic S-Docs Setup menu, which controls configuration for the classic editor experience.
{% endhint %}

### Getting Started

To access these configurations

* Navigate to the Lightning menu within the S-Docs application in Salesforce.
* Select the **S-Docs Settings** page.

#### E-Signature Configuration Wizard

To setup initial configuration for the running admin user click the **Run Setup Wizard** button to initiate the process.

#### Step 1: Setup your Force.com Site

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

{% hint style="info" %}
To support the e-signature signer experience, configure a new Salesforce Force.com Site. If a site has not yet been created for your Salesforce org, go to **Setup > Sites**, create a new site and ensure that **Lightning Features for Guest Users** enabled.
{% endhint %}

1. Select the Force.com site from the dropdown list
2. Click **Start Configuration**

#### **Step 2: Assign Permissions**

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

This step of the process conveniently runs automatically, assigning sender permissions to the running user profile and and sets guest base permissions so signers can access the site to sign their documents.

{% hint style="info" %}
If you need to assign additional permissions to additional users, navigate to **Setup > Users** and select the user profile. Click **Permission Set Assignments > Edit Assignments** and assign the **S-Docs E-Signature Sender** permission set from the multi-select picklist.
{% endhint %}

Click **Finish Setup.**

<figure><img src="/files/tBf82sgJmH1HqiSwMpWL" alt=""><figcaption><p><em>When e-Signature configuration is successful, the Settings Interface will display this message.</em></p></figcaption></figure>

***

### Global e-Signature Settings

The global *e-Signature Settings* configuration wizard establishes organizational defaults exclusively for the new S-Docs e-Signature functionality.

{% hint style="info" %}
These configurations apply only to the new e-Signature feature and do not affect classic S-Sign setups.
{% endhint %}

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

#### Identity Verification

* **PIN Authentication:** Enable this setting to require PIN authentication for all signers. When active, this security measure applies to all requests by default unless explicitly modified in the *e-Signature Request Builder* for a specific document.

***

<figure><img src="/files/2mnDTq9PyTNbUOzVrYSD" alt=""><figcaption></figcaption></figure>

#### Expiration & Notifications

* **Expiration Window:** Define the number of days signers have to complete a request before it expires. This is set to 30 days by default, but can be updated to any value your business requires.

***

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

#### Redirection

* **Signer Redirection:** Specify the URL where signers are redirected after completing a document. By default, signers are redirected to the S-Docs website, but this can be customized to redirect to your company or client website.

***

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

#### Disclosures

* **Legal Disclosures:** Add legal copy and/or a link to your organization's legal and informational disclosures under the *Disclosure* section. This information will be displayed within all automated emails sent by S-Docs.

***

<figure><img src="/files/3deJ9IQTi1aFcgF02wCf" alt=""><figcaption></figcaption></figure>

#### Record Association & Audit Trails

* **Audit Trail Placement:** Choose how to generate and store the final audit log. Select whether to append the audit trail to the end of the signed document, create it as a separate document, or choose not to generate an audit trail at all.
* **Signature Metadata:** Choose whether to visually display the time stamp and the signer's name alongside the signature image within the document.
* **Source Record Attachment:** Toggle *Attach to Record* to automatically attach the finalized, signed PDF back to the source Salesforce record once the workflow concludes.


---

# 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/configure-s-docs-e-signature-and-global-settings.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.
