# 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.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FGM6nQvgIryNpBkPYzxEc%2FScreenshot%202024-01-31%20at%209.24.29%20PM.png?alt=media&#x26;token=31709d51-6066-42d5-a4ce-8acfe74f9809" alt=""><figcaption></figcaption></figure>

## 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](https://docs.feathery.io/build-forms/actions#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:<DOCUMENT_ID>}}`, where `<DOCUMENT_ID>` 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.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FVdQ6Fd8nwrfxhjLfkp7E%2FScreenshot%202023-11-27%20at%2012.25.11%20AM.png?alt=media&#x26;token=5d3d9ca5-9f12-430a-baa9-708c5336f508" alt="" width="375"><figcaption></figcaption></figure>

### 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).