> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/forms-and-esignature/e-signature.md). # E-signature Collect signatures on a PDF from one or more recipients, with an audit certificate added to the signed document. {% hint style="info" %} Available on the **Professional** and **Enterprise** plans, and during the free trial. {% endhint %} E-signature is built on [fillable forms](/forms-and-esignature/fillable-forms.md). You add a **Signature** field to a form, and your recipient signs on the request page. They don't need an account. ## Add a signature field 1. Attach a PDF to a checklist item and click **Create Form** (or **Edit Form**). 2. Drag **Signature** from the **Form Fields** panel to where the recipient should sign. 3. Click the field. Under **Assignment**, choose who signs it. Under **Signature**, choose **Type or draw**, **Draw only** or **Type only**. 4. Add a **Date** field next to it if you want the signing date. It fills in automatically when that signer finishes. 5. Click **Save Form**. ## How your recipient signs The recipient clicks the signature field. They type their name or draw their signature, read the agreement ("By providing your signature below, you agree that this is legally binding, just like a handwritten signature."), and click **I Agree**. Then they choose **Submit Form**. Their walkthrough is in [Fill and sign a form](/for-your-clients/fill-and-sign-a-form.md). Before signing, Pipefile checks who the signer is. The link you send is personal to each recipient. If they open the form on another device or come back to it later, Pipefile may send them a 6-digit code by email or text to confirm it's them. ## Multiple signers Every recipient on a request has a role. When you add recipients, Pipefile names their roles **Recipient**, **Recipient 2** and so on, each with its own color. To rename a role, click **Edit role name** (the pencil next to the role on the recipient's card), for example "Client" and "Spouse". In a template, set the roles under **Recipient Roles** with **Add Role**. When you send from the template, each role gets its own recipient. In the form builder, assign each field to a role: * **Signature** and **Date** fields always belong to one role. New ones go to the first role until you change them. * **Text** and **Checkbox** fields can belong to one role or stay **Unassigned**. Any recipient can fill an unassigned field. Each signer sees the fields for other roles locked, marked **Awaiting** and the role name. All signers work on the same copy of the form, so one person's answers are visible to the others. Signers can sign in any order. When one signer finishes but others haven't, they see **Your Part is Complete**. The checklist item stays open until every signer has signed. Automated reminders skip signers who have already done their part. On the request dashboard, a clock icon next to the uploaded form means it is still waiting on signers. Hover over it to see who has signed and who hasn't. ## The audit certificate When a form is signed, Pipefile creates a **Certificate of Completion**. It is added to the end of the PDF when you download, preview or export the signed form. It lists the document title and form ID, and for each signature: * Signer name, email and phone * Role and the field they signed * How they were verified, and the email address or phone number used * IP address and device (browser and operating system) * When they viewed the request, signed, and completed their part If a signature is later voided, the certificate keeps the entry, marks it **\[VOIDED]** and records when and why. ## When signatures are voided A signature stays valid only while the form it was given on is unchanged. Pipefile voids signatures in these cases: * **A signer edits a shared field after someone else signed.** Before the change is allowed, the signer sees **Editing this field will void existing signatures** and must choose **Void & Continue**. The people whose signatures were voided get an email asking them to sign again. * **You reject the signed form's file.** Rejecting a signed form voids its signatures. Pipefile shows **Rejecting will void signatures** and lists the affected forms. Click **Void and continue** to go ahead. If you reject or mark the item incomplete in a checklist item review, signers are emailed to sign again. If you only reject the file, signers aren't emailed, so tell them if they need to sign again. Undoing the rejection restores the signatures. * **The person who first opened the form starts over.** Starting over clears the form and every signature, and everyone has to fill and sign again. * **A signer removes their own signature** by clicking it and choosing **Remove signature**. Voided signatures are never deleted. They stay on the audit certificate with the reason. ## Related * [Fillable forms](/forms-and-esignature/fillable-forms.md) * [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md) * [Download and export to PDF](/reviewing-and-exporting/download-and-pdf-export.md) --- # 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://support.pipefile.com/forms-and-esignature/e-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.