> 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/s-sign-with-pdf-upload.md).

# S-Sign with PDF-Upload

This guide covers the integration of S-Docs PDF-Upload with S-Sign, allowing you to use existing PDF files as templates while overlaying e-signature fields via a drag-and-drop interface.

***

The PDF-Upload feature is ideal for organizations that have pre-formatted PDF forms (like government or industry-standard docs) and want to add S-Sign capabilities without rebuilding the document in HTML.

### 1. Initial Setup

Before configuring the template, ensure the Template Format field on the S-Docs Template object includes "PDF-Upload" as a picklist value.

* Template Creation: Create a new S-Docs template and set the Template Format to `PDF-Upload`.
* Enable S-Sign: 1. Navigate to the Advanced Options tab.

  2\. Find the E-Sign Vendor dropdown and select `S-Sign`.

  3\. Crucial: Click Save before attempting to add signature fields.

***

### 2. Accessing S-Sign Settings in PDF-Upload

Unlike standard HTML templates, the S-Sign settings menu is integrated directly into the PDF-Upload workspace.

* Navigation: Go to the Upload PDF tab in your template.
* Creating Fields: Click the Create Another Field button.
* Field Type: You will now see S-Sign Field available as a type.
* Global Settings: To access the full S-Sign configuration (signer profiles, reminders, etc.), click the S-Sign Settings link located at the bottom of the PDF-Upload settings menu.

***

### 3. Placing Signature Fields

The PDF-Upload editor uses a "Drag & Drop" mechanism to position S-Sign inputs exactly where they need to be on the static PDF pages.

| **Feature**         | **Description**                                                                                                                                  |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Drag & Drop         | Once a field is created, drag the S-Sign Input tag from the sidebar onto the document preview.                                                   |
| Re-Drag             | If a tag is placed incorrectly, use the Re-Drag Merge Field button to reset its position and try again.                                          |
| Field Customization | Switch back and forth between "Field Settings" and "S-Sign Settings" to adjust attributes like *Required* status or *Signer Profile* assignment. |

***

### 4. Key Configuration Highlights

* Signer Profiles: You can still define multiple signers (Signer 1, Signer 2, etc.) and assign specific drag-and-drop fields to each one.
* Compatibility: All standard S-Sign field types (Signature, Initials, Text, Checkbox, Date) are supported within the PDF-Upload editor.
* Final Output: The finished document will maintain the exact layout and formatting of your original uploaded PDF, with the e-signature elements layered on top.

***


---

# 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/s-sign-with-pdf-upload.md?ask=<question>&goal=<user_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.