Document signing

Send a document for signature

1. Open Signatures → New envelope and upload a PDF up to 25 MB and 200 pages. Add an optional Customer, message, expiry date, and choose parallel or ordered routing.
2. Add each signer's name and email. Add copy recipients when someone should receive the completed document without signing it.
3. Place fields on the PDF. Every signer needs at least one signature field; name, email, date, initials, text, and checkbox fields can be required or optional.
4. Review the request and click Send. Genosyn freezes the source, recipients, fields, and routing so the agreement cannot change under a signer.

What the signer sees

Each recipient receives a separate high-entropy link. The link is the credential: its secret is never stored in the database, and sending a reminder replaces the prior link. The signer reviews the exact PDF, completes their assigned fields, consents to electronic records, and submits. They can also decline and give a reason. Signers do not need a Genosyn account. Date-signed fields use the signer's local calendar date; Genosyn binds the reported timezone and offset into the tamper-evident completion evidence.

• Parallel routing sends every signer at once.
• Ordered routing sends only the first routing group. The next group is invited after every signer in the current group finishes.
• A completed request emails every signer and copy recipient the final PDF and keeps a download available from the request page.

Completed PDF and evidence

Genosyn preserves the uploaded source and its SHA-256 fingerprint, stamps completed values into a new PDF, and appends a completion certificate. The certificate lists the document fingerprint, recipients, timestamps, consent, and the append-only event trail. Events form a hash chain, and each signer's accepted field values are bound to that chain with a canonical SHA-256 manifest printed on the certificate. International names and field values are embedded with licensed Unicode fonts; Genosyn rejects unsupported or non-fitting text before recording consent instead of silently changing it. A Customer-linked completion is also archived under Customers → Contracts.

AI-native preparation and follow-through

Under Signatures → AI access, owners and admins choose one company-wide level per AI Employee. Signing tools stay deferred until the employee searches for them.

Read

List requests, inspect recipients, fields, status, and evidence.

Draft

Prepare a request from a PDF Resource Grant, configure recipients and fields. It cannot contact anyone.

Send

Send, remind, or void a prepared request. Every action is attributed to the AI Employee in the audit log and journal.

AI Employees can never call the public signer completion endpoint or supply a recipient's signature. Ask them to draft an NDA, route the next agreement, chase outstanding signers, or summarize completion evidence; the recipient's act remains human.

Control the lifecycle

Senders can resend an individual recipient's link, void an active request with a reason, duplicate an existing request into a fresh draft, or download the original and completed PDFs. An expiry stops every outstanding link. Declined, voided, expired, failed-delivery, and completed states remain visible instead of disappearing, and every transition is evidence in the request timeline.

Delivery attempts also appear under Settings → Email Logs. Backups include the database metadata and both PDFs under the company's data directory.