BlogTag
Envelope admin
Void, correct, or resend an in-flight envelope, and what happens when a signer declines.
Related product pages
Guides
Envelope admin: void, correct, resend, and when signers decline
How Inkpacket handles an in-flight envelope: signer decline with a reason, void (links stop), correct the recipient on the same envelope, and resend the existing signing link.
Public API and signed webhooks for developers
Mint an org-scoped Bearer token, create envelopes from a template, send with an optional access code, and verify HMAC-SHA256 webhook signatures on the envelope lifecycle.
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.
When to void, correct, or resend an envelope
Pick the Inkpacket envelope-admin verb that keeps the same envelope id: void when the deal is off, correct when the recipient is wrong, resend when the link never arrived.
Correct, void, or decline an envelope
Pick the Inkpacket verb that matches the mess: correct when the recipient is wrong, void when you stop the deal, decline when the signer refuses. One decline closes the envelope. Completed envelopes cannot be changed.
Resend after a soft-fail email
When Inkpacket skip-logs a signing invite, Envelope admin Resend emails the same token again — or logs again. The envelope stays. That resend-after-soft-fail honesty is not a second envelope and not a seat invite.
Document list aging and status honesty
Inkpacket Documents lists draft, sent, completed, voided, expired, and declined. The hourly cron marks overdue SENT envelopes expired so the list stays honest. Aging is a status change, not a delete. That is list-aging honesty.
Void after a partial sign
An Inkpacket envelope stays SENT after the first signer marks it. Void still works. Later links die. You cannot un-sign or void a completed envelope. That is partial-void honesty — not a rewrite of the audit.
Correct an envelope mid-flight
Correct the outstanding signer on a sent Inkpacket envelope — name, email, or phone — without minting a twin. The previous token retires when the email changes. That is mid-flight-correct honesty, not void-and-recreate.
Decline closes the envelope
One Inkpacket decline closes the whole envelope — later sequential signers are not invited, parallel links die, reminders stop. That is decline-close honesty, not a per-signer skip.
What the audit log records
An Inkpacket envelope records created, sent, viewed, signed, completed, declined, voided, corrected, and expired. It does not record PIN tries, plaintext codes, or card data. That is audit-record honesty — the desk log, not a mystery export.
Void after a partial sign versus decline
After someone has marked an Inkpacket envelope, the sender can still void. A later signer can still decline. Both close the envelope. That is void-versus-decline honesty — two verbs, one dead envelope, not an un-sign.
Email change retires the signing token
On an Inkpacket correct, changing the outstanding email retires the previous token. A name-only or phone-only fix can keep it. That is token-retire honesty — not resend, not a twin envelope.
Void does not email the signer
Voiding an Inkpacket envelope kills every signing and embed link. It does not email the signer. The link simply dies. That is silent-void honesty — tell outstanding people out of band.
Resend does not rotate the signing token
Inkpacket Resend emails the existing signing link. The token stays. Only an email-change correct retires it. That is same-token-resend honesty — not a new envelope, not a new URL.
Phone-only correct keeps the signing token
Correcting only the phone — or only the name — on a sent Inkpacket envelope keeps the signing token. Only an email-change correct retires it. That is phone-correct honesty, not a rotate and not a twin envelope.
Why completed envelopes cannot be changed
Once an Inkpacket envelope is completed, the stamped PDF is the record. You cannot void, correct, or resend it. That is completed-lock honesty — not a hidden edit, not a rewrite of the audit.
Why a decline reason is required
An Inkpacket decline needs a reason — 500 characters or fewer. An empty reason is rejected. That is decline-reason honesty, not a void and not a silent refusal.
Why only sent envelopes can use void, correct, or resend
Inkpacket void, correct, and resend work on SENT envelopes only. Draft, completed, expired, declined, and already-voided ids hide those controls. That is sent-only-admin honesty — not a missing Settings toggle.
Why This envelope is already voided is not a completed lock
Inkpacket returns This envelope is already voided when you void an envelope that is already voided. That is already-voided honesty — not a completed lock, not checkout.
Why There is no outstanding signer on this envelope is not a completed lock
Inkpacket returns There is no outstanding signer on this envelope when correct or resend finds nobody left to act. That is no-outstanding honesty — not a completed lock, not checkout.
Why This envelope was already declined is not a completed lock
Inkpacket returns This envelope was already declined on a second decline, and This envelope can no longer be declined when status is not sent. That is already-declined honesty — not a completed lock, not checkout.
Why That signer is not outstanding on this envelope is not a completed lock
Inkpacket returns That signer is not outstanding on this envelope when correct names someone who already finished. That is named-signer honesty — not an empty outstanding list, not checkout.
Why a no-op correct is not a completed lock
Inkpacket returns Change the signer name, email, or phone to correct this envelope when correct posts the same values already stored. That is no-op-correct honesty — not a finished signer, not checkout.