# Email Settings Tab

Use **Email Settings** to control what happens when users email generated documents.

This tab sets default email values, controls which fields users can edit, and helps enforce sender and recipient rules.

{% hint style="info" %}
Use **Email Settings** for email recipients, sender controls, and delivery guardrails.

Use **Document Options** for file behavior and general generation settings.

Use **Create Salesforce Task** for follow-up task automation.
{% endhint %}

### What you can configure in Email Settings

The **Email Settings** tab includes four main areas:

* **Email Subject Settings** — control the default subject and whether users must keep or enter one.
* **Email Recipient Settings** — control default recipients and whether users can change them.
* **Email Sender Settings** — control the sender address and available sender choices.
* **Other Email Settings** — control body locking, domain restrictions, and translation behavior.

Use single-brace syntax in email setting formulas: `{!Object.Field}`.

### Email subject settings

Use this section when you want consistent email subject lines.

| Label                    | Description                                     |
| ------------------------ | ----------------------------------------------- |
| **Subject**              | Set the default subject line for the email.     |
| **Lock Subject**         | Prevent users from changing the subject line.   |
| **Require subject line** | Require a subject before the email can be sent. |

Use merge fields in the subject when you want record-aware email titles.

Examples:

* `Quote for {!Opportunity.Name}`
* `Invoice {!Invoice__c.Name} from Your Company`

### Email recipient settings

Use this section to prefill or restrict who receives the email.

| Label             | Description                                         |
| ----------------- | --------------------------------------------------- |
| **To**            | Set the default primary recipient list.             |
| **Lock To**       | Prevent users from changing the **To** field.       |
| **CC**            | Set default carbon copy recipients.                 |
| **Lock CC**       | Prevent users from changing the **CC** field.       |
| **BCC**           | Set default blind carbon copy recipients.           |
| **Lock BCC**      | Prevent users from changing the **BCC** field.      |
| **Reply To**      | Set the address that receives replies.              |
| **Lock Reply To** | Prevent users from changing the **Reply To** field. |

Separate multiple email addresses with commas.

You can combine static addresses and merge fields in the same field.

{% hint style="warning" %}
If a locked email field is blank, S-Docs hides it on the email screen.

If **To** is locked and blank, the user will not be presented with the option to email through the legacy visualforce page method. 
{% endhint %}

### Email sender settings

Use this section to control who the email appears to come from.

| Label                                            | Description                                                                  |
| ------------------------------------------------ | ---------------------------------------------------------------------------- |
| **From**                                         | Set the default sender as the logged-in user or a verified org-wide address. |
| **Restrict to Org-Wide Addresses**               | Force emails to send from org-wide addresses only.                           |
| **Enable user to choose/select from a picklist** | Let users choose from allowed sender addresses at send time.                 |
| **Use Salesforce Email Signature**               | Enable the Salesforce email signature merge field in the email body.         |

By default, S-Docs can send from the user who generated the document.

{% hint style="info" %}
Use a verified org-wide address when you need a shared sender such as `billing@company.com`.

Use `{{{!UserSignature}}}` in the email body when you want to insert the generating user's Salesforce email signature.
{% endhint %}

### Other email settings

Use this section for email delivery guardrails and body controls.

| Label                             | Description                                                          |
| --------------------------------- | -------------------------------------------------------------------- |
| **Email domain restriction**      | Limit sending to approved recipient domains only.                    |
| **Translate Email Settings Data** | Apply Data Map translations to merge field values in email settings. |
| **Lock Body**                     | Prevent users from editing the email body before sending.            |

Enter restricted domains as a comma-separated list such as `company.com,partner.org`.

Do not include spaces, `@`, or `www`.

S-Docs validates **To**, **CC**, and **BCC** against the allowed domains when the user clicks **Send**.

### Related guides

* [Email Delivery and Security](/sdocs/template-architecture/template-settings/email-settings-tab/email-delivery-and-security.md)
* [How To: Sending Generated Documents via Email](/sdocs/automation-and-document-lifecycle/workflows/sending-generated-documents-via-email-s-docs-lwc.md)
* [How To: Email Editor In Flow](/sdocs/automation-and-document-lifecycle/automate-with-flow/how-to-email-editor-in-flow.md)


---

# Agent Instructions: 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:

```
GET https://help.sdocs.com/sdocs/template-architecture/template-settings/email-settings-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.