> 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/s-sign/template-configuration-fields-profiles-settings/creating-an-s-sign-enabled-template.md).
# Creating an S-Sign Enabled Template
Add the S-Sign Template Editor to begin building a template with signer inputs.
S-Sign can be enabled and configured in any template with the **HTML**, **PDF**, or **PDF Upload** format.
## Enable S-Sign
In the **Classic** S-Docs Template Editor, navigate to the Advanced Options tab and check the "Enable S-Sign" option at the top. This will add the S-Sign Template Editor to the PDF-type editing views.
## Navigating to the Classic Template Editor
As of our Summer '26 release, new **PDF** and **PDF Upload** templates will automatically open in the [Visual Template Editor](https://help.sdocs.com/sdocs/visual-template-editor/visual-template-editor-overview). To enable S-Sign, template builders must first navigate back to the **Classic** editor.
{% hint style="info" %}
Existing S-Sign enabled templates that are cloned will retain the Classic editor with S-Sign editor.
{% endhint %}
### PDF Format
In the Visual editor, click the Settings iconin the upper left corner to open the Settings menu. At the bottom of the Documents section, click **Switch to Classic S-Docs Editor**.
{% hint style="info" %}
Making this switch will lose any changes made in the Visual editor.
{% endhint %}
### PDF Upload Format
An administrator can add the **SDocs Revert PDF Upload Editor** Lightning Web Component to the S-Doc Template page layout.
{% hint style="info" %}
Update Component Visibility to only show this LWC for PDF Upload template records.
{% endhint %}
Once this LWC is in place, template builders can click this button after creating their PDF Upload template **before** they open the editor.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.sdocs.com/s-sign/template-configuration-fields-profiles-settings/creating-an-s-sign-enabled-template.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
in the upper left corner to open the Settings menu. At the bottom of the Documents section, click **Switch to Classic S-Docs Editor**.
