BlogTag
Electronic signatures
What electronic signature software is, how an envelope moves from PDF to filed copy, and which Inkpacket screens back that loop.
Related product pages
Guides
What is electronic signature software?
A plain-language pillar on electronic signature software: envelopes, fields, signing links, audit events, and the workspace features that keep a send on track.
How to send a document for signature in under 5 minutes
A timed walkthrough: open a workspace, upload a PDF, place signature fields, set reminder and expiry, and send a signing link — including the copy-link fallback when mail is not configured.
Choosing a plan: Free vs paid lanes
How to pick an Inkpacket lane: Free at 5 packets a month and 1 published Web Form, then Starter at 20 envelopes with 3 Web Forms — more envelopes than Free. Same desk — including sequential and parallel routing — on every plan. Billing is published, not charging.
What a completed envelope includes
After every Inkpacket signer finishes, pdf-lib stamps values onto a second stored PDF. Download it from the envelope, read the audit events, and optionally archive to Drive when credentials are set.
How to read an Inkpacket audit trail
Read created, sent, viewed, signed, completed, declined, voided, corrected, and expired on an Inkpacket envelope — what each event proves, what it does not, and when webhooks or Drive export the same log.
What is a signing envelope?
A signing envelope is the Inkpacket envelope around one PDF: fields, recipients, a tokenized link, and an audit trail from draft to filed copy — not a chain of forwarded files.
Where uploaded PDFs are stored
Inkpacket stores each uploaded PDF on the envelope — S3-compatible when the S3_* keys are set, otherwise Local fallback. Drive archive is a separate completed-packet export and reports Drive not configured without credentials.
When Drive archive soft-fails
Coming soon. Google Drive archive copies a completed Inkpacket PDF and audit JSON to a folder you choose. Without credentials the desk reports Drive not configured and does not pretend the upload happened. The envelope still completes.
Settings storage: S3 versus local
Inkpacket Settings → File storage shows S3-compatible when the S3_* keys are set, otherwise Local fallback. Uploads still work. GET /api/v1/health reports storage.configured and storage.backend. That is settings-storage honesty — not Drive.
Settings email From and Reply-To
Inkpacket Settings → Outbound email shows emailConfigured only. From is RESEND_FROM_EMAIL or Inkpacket <noreply@inkpacket.com>. There is no workspace Reply-To field. That is from-line honesty — not a branded inbox you type in Settings.
Mobile desk hamburger menu map
On a phone, Inkpacket’s desk sidebar is Open desk menu — a hamburger drawer at #desk-mobile-nav. Help is not a row. That is hamburger-map honesty, not a missing Team page.
Workspace switcher versus mobile drawer
On a phone, Inkpacket’s workspace switcher sits above Open desk menu. The drawer is #desk-mobile-nav. Help and Sign out are not rows. That is switcher-versus-drawer honesty — two chrome pieces, not a missing Team page.