> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/elements/fields/signature.md).
# Signature
The Signature field presents a canvas that users can use to draw a signature.
The `Signature` field allows you to collect a signature from the user. Feathery allows you to collect legally-binding signatures.
## Signature Methods
You may toggle the available signature methods for users. They can either type, draw, or do both to generate their signature.
## Signature Workflows
You may want to use Feathery's [collaboration workflow feature](/platform/collaborative-workflows/collaboration.md) to invite multiple users to collaborate on a single form, collect multiple signatures in one submission, and restrict each user to filling out specific form sections.
Feathery [Documents](/platform/document-autofill-and-signatures.md) also allow you to collect e-signatures directly on documents with the same signature element.
### For Developers
The Feathery SDK and API reference signature fields with `type` equal to `signature`. The submitted value is a `File`.
To trim the whitespace around the signature, it's best to perform server-side processing on your image file.
---
# 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://docs.feathery.io/platform/build-forms/elements/fields/signature.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.