> 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/developer-hub/document-workflows/s-docs-lwc-reference/documents-s-docs-settings.md).

# Documents (S-Docs) Settings

Use this page when you need the exact configuration options for **Documents (S-Docs)**.

This component shows generated files and supports post-generation actions on a Salesforce record page.

### Settings

<table data-full-width="true"><thead><tr><th>Setting</th><th>Use it for</th><th>Key behavior</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>Set the component header on the record page.</td><td>Recommended value: <code>Generated Documents</code></td></tr><tr><td><strong>Object API Name</strong></td><td>Define which record's generated files the component shows.</td><td>Must match the object used in <strong>Generate Documents (S-Docs)</strong>.</td></tr><tr><td><strong>Email Template</strong></td><td>Load one predefined HTML email template for send actions.</td><td>One email template can be configured per component. If none is selected, users can still send manually. The template must be valid for the object.</td></tr><tr><td><strong>Automatically Open Email Editor</strong></td><td>Open the email composer right after generation.</td><td>Best when users usually email documents immediately after creating them.</td></tr><tr><td><strong>Show Refresh</strong></td><td>Show the <strong>Refresh</strong> action for generated files.</td><td>Refresh updates the existing document with current Salesforce data, creates a new version, keeps the original template and layout, and does not run a full regenerate flow.</td></tr><tr><td><strong>Show Versions</strong></td><td>Show version history for generated files.</td><td>New versions are created by <strong>Refresh Data</strong> and <strong>Live Edit</strong>. The latest version stays active by default.</td></tr></tbody></table>

{% hint style="info" %}
Use the same **Object API Name** on both record-page components.

Use **Email Template** when users send the same message often.

Enable **Show Refresh** and **Show Versions** together when users need traceability.
{% endhint %}

### Related pages

* [S-Docs LWC Reference](/developer-hub/document-workflows/s-docs-lwc-reference.md)
* [How To: Sending Generated Documents via Email](https://github.com/kvantiem-sdocs/Developer-Hub-Documentation/tree/main/automation-and-document-lifecycle/workflows/sending-generated-documents-via-email-s-docs-lwc.md)
* [How To: Refresh Document Data Within the Documents](https://github.com/kvantiem-sdocs/Developer-Hub-Documentation/tree/main/automation-and-document-lifecycle/workflows/refresh-document-data-within-the-documents-s-docs-lwc.md)
* [How To: View Document Versions in the Documents LWC](https://github.com/kvantiem-sdocs/Developer-Hub-Documentation/tree/main/automation-and-document-lifecycle/workflows/view-document-versions-in-the-documents-lwc.md)
* [How To: Editing Generated Documents](https://github.com/kvantiem-sdocs/Developer-Hub-Documentation/tree/main/automation-and-document-lifecycle/workflows/editing-generated-documents-live-edit.md)


---

# 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/developer-hub/document-workflows/s-docs-lwc-reference/documents-s-docs-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.