Document Signing

Send any document for e-signature without leaving your workspace: proposals, contracts, offers. Recipients get a secure one-time link by email, confirm consent to sign electronically, complete the fields you chose, and every step lands in a tamper-evident audit trail. Find it under CRM > Signatures, or press Send for signature on a contract to start a request already addressed to that contract’s client.

• Send flow: attach one or more documents with the Drive picker (it only shows drives and files you can access, RBAC-enforced), or send title-only; add signers and CC viewers, choose the fields each signer completes (signature, initials, auto-date, text, checkbox), then Save & send. An optional expiry date kills the links automatically. Signers see every attached document, each streamed through the same token-checked, malware-scan-gated endpoint.
• Consent + intent, before signing, each signer explicitly agrees to do business electronically (ESIGN/UETA-style). They can **draw** their signature (mouse or finger) or **type** their full legal name; the date stamps itself automatically. Drawn signatures are captured as a compact image and appear on the certificate of completion.
• Place fields on the document: when the primary attachment is a PDF, use “Place on document” in the send flow to drag signature, initials, date, text and checkbox fields onto the exact spot on each page. Coordinates are stored as page-fractions, so the field value is stamped in that position on the final signed PDF. Fields you don’t place stay as a simple list the signer fills in. Placement is optional. When you place fields, the signer completes them **directly on the rendered document** (DocuSign-style), exactly where they sit on the page.
• Signing order: tick “Sign in order” in the send flow and signers are unlocked one at a time, top to bottom: each signer’s link stays in a waiting state until everyone above them has signed (enforced on the server, not just the UI). Leave it off for parallel signing, where everyone can sign at once.
• Completion copies: when the last signer finishes, every party (signers and CC viewers) is automatically emailed a link to view the fully-signed document, and the request fires “document.signed” for your automations.
• Signers see the document. The signer page renders the document itself: if fields were placed, the signer fills them in place on the page (with an inline preview + View link otherwise), all streamed through the token-checked, malware-scan-gated endpoint; document views are recorded in the audit trail.
• Tamper-evident audit trail: every event (sent, viewed, consented, signed, declined, completed) is hash-chained: each entry cryptographically references the one before it, so any alteration is detectable. The chain is visible on the request detail.
• Workflow-ready: completion raises a "document.signed" event, a decline raises "document.declined", and an unsigned request that passes its expiry raises "document.expired", so Automations can create tasks, notify owners, or update your pipeline the moment ink lands (or doesn’t).
• Owner alerts: signed, declined and expired all notify workspace owners/admins in-app (bell) through the notification centre; each is an individual toggle under Settings ▸ Notifications, so you can opt in or out per person.
• Control: drafts are editable until sent; sent requests can be voided at any time (links stop working immediately). Only the request creator or a workspace owner/admin can send, void or delete.
• Certificate of completion: every completed request has a printable certificate: the parties, their consent and signing times, the signed values, and the full hash-chained audit trail with a verification note. Open it from the request detail and print or save as PDF.
• Signed-PDF export: on a completed request, Download signed PDF assembles the final packet on demand: the original document with a per-page “electronically signed via {workspace}” footer (and any placed field values), followed by the tamper-evident Certificate of Completion page. It is generated fresh in memory and streamed straight to you (nothing new is stored) and the source is only embedded after passing the same malware-scan gate signers go through.

1. 1

   Create the request

   CRM > Signatures > New request. Give it a title, pick the Drive document, add your message and an optional expiry.

2. 2

   Add recipients & fields

   Add each signer (and any CC viewers), then the fields to complete. Signature and date fields are pre-added for the first signer. For a PDF, use “Place on document” to drag fields onto the exact spot on the page.

3. 3

   Send

   Save & send: each recipient gets an email with their own secure link. Watch statuses move from pending to viewed, consented and signed on the request detail.

4. 4

   Act on completion

   When the last signer finishes, the request completes and fires "document.signed", wire an automation, or just check the audit trail with its hash chain.