Signature requests and Fill & Sign

Signature requests collect signatures on a PDF through recipient-specific links and retain an audit history. Start in Signature requests and choose the signing model carefully because it determines the output.

Who will sign?

• One person: send one secure signing link to one email address.
• Multiple people: collect signatures from at least two people.
• Only me: add your own signature and download the PDF without emailing external signers.

For Multiple people, choose the desired output:

• Single document with all signatures: everyone signs the same shared document. Use this when one final agreement needs every signature.
• Separate copies, individually signed: each signer receives a separate copy. Use this for acknowledgements or forms where each person should produce their own signed document.

Create the request

1. Choose the signer model and, for multiple people, the output model.
2. Drag in or browse for a PDF.
3. Enter one valid signer email, or at least two comma-separated emails for multiple people.
4. Add an optional message of up to 1,000 characters.
5. Review and choose Send for signature, or Sign and download for Only me.

The underlying implementation supports signature/text/date/checkbox fields and a tamper-evident event history. Where the builder exposes placement controls, assign fields to the intended signer and page before sending.

Routing and progress

Request details show status, signed/total progress, routing mode, expiration, and each recipient's state such as awaiting, viewed, or signed. Multiple signers may be handled in parallel or in a configured order depending on the request workflow.

Reminders and editing

Edit the request title, message, and automatic reminder interval: none, daily, every 3 days, or weekly. You can also send a reminder manually.

Recipients, document, and fields lock after sending to preserve the audit trail. If those are wrong, cancel the request and create a new one rather than mutating the signed context.

Cancel, expire, decline, and delete

Canceling revokes outstanding signing links. Completed requests retain their audit history. Draft, declined, expired, or canceled unsigned requests can be deleted when permitted. A signed document and audit trail support evidence, but enforceability depends on jurisdiction, intent, identity, consent, and the transaction; obtain legal advice for high-stakes use.

Security limits

Recipient-specific links reduce accidental sharing but are not the same as government-ID identity verification. Anyone with access to a recipient's mailbox or forwarded link may be able to act. Use stronger authentication or an appropriate specialized service when the risk demands it.