> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/esignatures/creating-esignatures.md).

# Creating eSignatures

To create documents for eSignatures in Docupilot, follow this simple 3-step process:

## Step1: Add Signature Fields to Your Template

Start by placing signature placeholders in your document template. These signature placeholders (such as `{{eSign ...}}`, `{{eInitials ...}}` etc.) indicate the locations where signers will be prompted to sign or fill in information during a signing session.

For detailed instructions, refer to our guide: [Placing Signature fields in your template](/deliveries/esignature.md#placing-signature-tags-in-document).

## Step2: Configure eSignature Delivery

Once your template includes all required signature fields, set up the eSignature delivery. This configuration determines the recipients, signing order, reminders and other signing preferences.

Learn how to configure it here: [Configuring eSignature Delivery](/deliveries/esignature.md#configuring-esignature-delivery)

## Step3: Generate the Document

When you [generate a document](/create-document.md) using this setup, an eSignature Envelope will be created and the signing process will be initiated. [Signature Invitations](/esignatures/signature-invitation.md) will be sent to respective recipients via email to review and sign.

## Troubleshooting issues

If you do not see an Envelope listed under eSignatures tab, here are the potential solutions:

1. Only a sender can see the envelope.
2. If you are the sender, but you still can't see the Envelope, there might be an issue in creating the Envelope. Navigate to [reports tab](/reports.md) to find out the error message.
3. If you need further help, [Ask the community](https://community.docupilot.com/c/ask-the-community/7) or reach out to our support.


---

# 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.docupilot.app/esignatures/creating-esignatures.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.