> 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/deliveries/signable.md).
# Signable
Send generated documents automatically for Signing.
Signable is a cloud-based electronic signature solution which enables a user(s) to send out documents electronically to be signed by one or more signers.
To set up an Signable Delivery, choose the `Signable` option from the list of deliveries available in the `Deliveries` tab.
Signable delivery configuration
## Signable Tags
Signable Tags is a feature that allows text to be used in documents as a placeholder for Signature, Date, Text, Upload and Checkbox. These tags will then be replaced with the relevant field.
One thing to remember when adding Tags to your template is to keep them on one line to ensure the Tag is retained. For example: `{signature:signer1:Please+Sign+Here}`
A tag has the following structure: **{WHAT:WHO:MESSAGE}**
{% hint style="warning" %}
Tags also do not support the use of characters other than A-Z, a-z, 0-9 E.g. “my+tag+name+/+label” is not valid.
{% endhint %}
{% hint style="warning" %}
Tags are ***Case-Sensitive***.
{% endhint %}
### Types of Signable Tags
Signable supports the following types of fields
* Signature
* Date
* Text
* Document Upload
* Checkbox
#### Signature:
Syntax: `{signature:who:message}`
Example:\
1\. {signature:signer1:please+sign+here}\
2\. {signature:signer2:please+sign+here}\
3\. {signature:signer3:please+sign+here}
### Optional Tags
A signable tag can be made optional by inserting a "?" after the first part of the tag.
Examples:
* `{text?:signer1:enter+name+here}`
* `{check?:signer2:Please+tick}`
* `{date?:signer3:select+date}`
### Adjusting the height and width of the tag
By default, the size of a tag is fixed to 10x100. This can be changed by mentioning the width and/or height of the tag while entering the tag.
Examples:
* `{text,w20,h30:signer1:enter+name+here}`
* `{check,w30:signer2:Please+tick}`
* `{signature,h40:signer3:sign+here}`
{% hint style="warning" %}
When providing both width and height for the tag, they shall be mentioned in the order of width and height only and not as height and width.\
\
Correct syntax: `{text,w20,h40:signer2:enter+age}`\
Wrong syntax: `{text,h40,w20:signer2:enter+age}`
{% endhint %}
---
# 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/deliveries/signable.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.
.jpg?alt=media&token=0e8a9173-b54d-4cb4-b044-419c707605b3)
