# Email Settings Quick Reference

Use this version when you want the same quick reference in table format.

{% 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 template cannot be emailed.
{% endhint %}

### Email Settings - Email Subject Settings

<table data-full-width="true"><thead><tr><th>Setting</th><th>Purpose</th><th>Type</th><th>Format</th><th>Behavior</th><th>Watch for</th></tr></thead><tbody><tr><td><strong>Subject</strong></td><td>Set the default email subject line.</td><td>Text field</td><td>Static text, merge fields, or both. Use single braces: <code>{!Object.Field}</code>.</td><td>Prefills the subject line. Null merge fields resolve to blanks.</td><td>Keep it short for mobile inboxes. Maximum length is 255 characters.</td></tr><tr><td><strong>Lock Subject</strong></td><td>Prevent users from changing the subject line.</td><td>Checkbox</td><td>On or off</td><td>When enabled, the subject field is read-only.</td><td>If enabled and blank, S-Docs hides the field.</td></tr><tr><td><strong>Require subject line</strong></td><td>Require a subject before send.</td><td>Checkbox</td><td>On or off</td><td>Validates the subject when the user clicks <strong>Send</strong>.</td><td>If the subject is already locked with a value, this setting has no practical effect.</td></tr></tbody></table>

**Examples:**

```
Quote for {!Opportunity.Name}
Invoice {!Opportunity.InvoiceNumber__c} from Your Company
Proposal for {!Opportunity.Account.Name}
Contract: {!Opportunity.Name} - Action Required
```

***

### Email Recipient Settings

<table data-full-width="true"><thead><tr><th>Setting</th><th>Purpose</th><th>Type</th><th>Format</th><th>Behavior</th><th>Watch for</th></tr></thead><tbody><tr><td><strong>To</strong></td><td>Set the default primary recipient list.</td><td>Text area</td><td>Single address, comma-separated addresses, merge fields, or a mix.</td><td>Prefills the <strong>To</strong> field. Users can edit it unless you lock it.</td><td>Separate multiple addresses with commas. This field must contain at least one valid recipient to send email.<br><br><a data-mention href="#recipient-field-examples">#recipient-field-examples</a></td></tr><tr><td><strong>Lock To</strong></td><td>Prevent users from changing <strong>To</strong> recipients.</td><td>Checkbox</td><td>On or off</td><td>Makes the <strong>To</strong> field read-only.</td><td>If enabled and blank, the template cannot be emailed.</td></tr><tr><td><strong>CC</strong></td><td>Set default carbon copy recipients.</td><td>Text area</td><td>Same format as <strong>To</strong>.</td><td>Prefills the <strong>CC</strong> field. Users can edit it unless you lock it.</td><td>Optional. If locked and blank, S-Docs hides the field.</td></tr><tr><td><strong>Lock CC</strong></td><td>Prevent users from changing <strong>CC</strong> recipients.</td><td>Checkbox</td><td>On or off</td><td>Makes the <strong>CC</strong> field read-only.</td><td>If enabled and blank, S-Docs hides the field.</td></tr><tr><td><strong>BCC</strong></td><td>Set default blind carbon copy recipients.</td><td>Text area</td><td>Same format as <strong>To</strong>.</td><td>Prefills the <strong>BCC</strong> field. BCC recipients stay hidden from other recipients.</td><td>If locked and blank, S-Docs hides the field.</td></tr><tr><td><strong>Lock BCC</strong></td><td>Prevent users from changing <strong>BCC</strong> recipients.</td><td>Checkbox</td><td>On or off</td><td>Makes the <strong>BCC</strong> field read-only.</td><td>If enabled and blank, S-Docs hides the field.</td></tr><tr><td><strong>Reply To</strong></td><td>Set the address that receives replies.</td><td>Text field</td><td>One email address or one merge field.</td><td>Sets the email Reply-To header. It can differ from the <strong>From</strong> address.</td><td>Only one reply-to value is supported. If locked and blank, S-Docs hides the field.</td></tr><tr><td><strong>Lock Reply To</strong></td><td>Prevent users from changing the reply-to address.</td><td>Checkbox</td><td>On or off</td><td>Makes the <strong>Reply To</strong> field read-only.</td><td>If enabled and blank, S-Docs hides the field.</td></tr></tbody></table>

#### **Recipient Field Examples**

```
{!Opportunity.Account.BillingEmail}
{!Contact.Email}
sales@company.com
{!Opportunity.Owner.Email}, manager@company.com
```

***

### Email Sender Settings

<table data-full-width="true"><thead><tr><th>Setting</th><th>Purpose</th><th>Type</th><th>Options</th><th>Behavior</th><th>Watch for</th></tr></thead><tbody><tr><td><strong>From</strong></td><td>Set the email sender address.</td><td>Picklist</td><td><strong>Logged in user</strong> or a verified org-wide email address.</td><td>Controls who the email appears to come from.</td><td>Org-wide addresses must already exist, be verified, and be available to the user.</td></tr><tr><td><strong>Restrict to Org-Wide Addresses</strong></td><td>Force senders to use org-wide addresses only.</td><td>Checkbox</td><td>On or off</td><td>Removes the ability to send from a personal user address.</td><td>Requires at least one allowed org-wide address.</td></tr><tr><td><strong>Enable user to choose/select from a picklist</strong></td><td>Let users choose the sender at send time.</td><td>Checkbox</td><td>On or off</td><td>Shows a sender dropdown with the user address and allowed org-wide addresses.</td><td>Most useful when multiple sender addresses are available.</td></tr><tr><td><strong>Use Salesforce Email Signature</strong></td><td>Enable the Salesforce signature merge field.</td><td>Checkbox</td><td>On or off</td><td>Makes <code>{{{!UserSignature}}}</code> available for the email body.</td><td>The user must have a Salesforce email signature configured. Use triple braces to preserve formatting.</td></tr></tbody></table>

***

### Other Email Settings

<table data-full-width="true"><thead><tr><th>Setting</th><th>Purpose</th><th>Type</th><th>Format</th><th>Behavior</th><th>Watch for</th></tr></thead><tbody><tr><td><strong>Email domain restriction</strong></td><td>Limit sending to approved recipient domains.</td><td>Text field</td><td>Comma-separated domains such as <code>company.com,partner.org</code>.</td><td>Validates <strong>To</strong>, <strong>CC</strong>, and <strong>BCC</strong> when the user clicks <strong>Send</strong>.</td><td>Do not include spaces, <code>@</code>, or <code>www</code>.<br><br><a data-mention href="#email-domain-restriction-examples">#email-domain-restriction-examples</a></td></tr><tr><td><strong>Translate Email Settings Data</strong></td><td>Apply Data Map translations to merge field values in email settings.</td><td>Checkbox</td><td>On or off</td><td>Translates merge field values in subject and recipient fields when Data Map translations exist.</td><td>It affects merge field output only. It does not translate static text.</td></tr><tr><td><strong>Lock Body</strong></td><td>Prevent users from editing the email body before sending.</td><td>Checkbox</td><td>On or off</td><td>Makes the email body read-only on the email screen.</td><td>Use it when the message must stay unchanged. Add <code>{{{!UserSignature}}}</code> if users still need signature personalization.</td></tr></tbody></table>

#### **Email domain restriction examples**

```
company.com
company.com,partner.com,client.org
company.com,company.co.uk,company.de
```

### Related guides

* [Email Settings Tab](/sdocs/template-architecture/template-settings/email-settings-tab.md)
* [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)


---

# 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/email-settings-quick-reference.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.