> 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/esignatures/introduction-to-esignatures.md). # Introduction to eSignatures Learn about eSignatures and key terminologies ## What Are eSignatures? **eSignatures**, or electronic signatures, allow individuals to sign documents digitally, eliminating the need for physical paperwork. They are legally recognized and secure. Docupilot supports *Advanced Electronic Signatures (AES)*, which comply with legal standards and include added verification, audit trails, and signer authentication to ensure trust and validity. ## What Is an Envelope? An *envelope* refers to a document or group of documents sent out for signing. It includes: * the document(s) to be signed * signer details * signature fields * reminder and expiry settings Each envelope in Docupilot gets a unique identifier, which is used to track its progress from start to finish. This envelope ID appears on all pages of the document(s) sent for signing. ## What is an Audit Trail? Audit Trail is a Document that shows the activity log of all the actions happened on an Envelope. For example, sent-viewed-signed-completed/declined, etc. This Audit log document bears the Envelope ID and acts as a proof of what stages Envelope has gone through. ## Type of Users for an Envelope * **Sender**: The user who initiates and sends the document for signing. * **Recipient**: The individual(s) who are required to sign or fill fields in the document. * **CC (Carbon Copy)**: Individuals who receive a copy of the envelope for visibility, but do not participate in signing. --- # 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/esignatures/introduction-to-esignatures.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.