> 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/document-autofill-and-signatures/signature-workflows.md).
# Signature Workflows
Feathery supports a combination of autofilling document templates and manually signing / entering information into the document as well.
## Standalone Signatures
You can manually invite users via email to sign documents or sign them directly yourself.
## Form-Initiated Signature Workflow
You can automatically fill document templates based on user interactions with a Feathery form. You can also optionally route the document out for signature / manual input afterwards.
All form-initiated workflows will start by prefilling the document with any existing form submission data that has been mapped to fields in the document.
### Redirect to Signature Flow
If you configure a button in your form with the [Sign Document](/platform/build-forms/actions.md#sign-documents) action, you'll be able to allow your form users to sign documents directly as part of the form flow.
### Email Invite to Signature Flow
#### Configure in Email integration
In your form email integration, you can add a link to an Feathery document for your email recipient to sign by including `{{FeatheryDocument:}}`, where `` is the unique ID of the document to sign.
The document to sign will already be [autofilled](#autofill-a-document-template-from-forms) with data from the current submission based on the relevant field mappings.
#### Configure in Documents
You can set up a fill trigger for your document template when a field value is changed or a form submission is completed.
For example, you may want to route a contract out for signature once a form submission is approved. You can annotate the document with a signature field, then set the document trigger to be when the approval status field value is changed to `Approved`.
When a submission is approved, the document will automatically be sent out for signature.
### Save Signed Document to Field
A link to your signed document can be saved to a hidden field. This can be configured under the **Signature Flow** section of your document settings. Once the URL is saved to the field, it can then be leveraged in your other integrations and logic (e.g. sent to a CRM).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.feathery.io/platform/document-autofill-and-signatures/signature-workflows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.