IpInkpacket

Blog

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.

Once the envelope is completed, the stamped PDF is the record. Envelope admin hides void, correct, and resend. The API returns Completed envelopes cannot be changed. That is completed-lock honesty: the filed copy stays filed, the envelope id stays put with a different verb than Void envelope, and you cannot un-sign or rewrite the trail from the same row.

In-flight admin is envelope admin: void, correct, resend, and when signers decline. After a mark but before everyone finishes, void after a partial sign. When the window ends instead, expired is not voided. Desk help is Docs. This guide is why Void envelope is missing after the last signer submits.

The FAQ says completed envelopes cannot be voided. Features names the filed file under completed PDF. Ask Inkpacket for completed envelopes cannot be changed to open this article. Ask what does completed envelopes cannot be changed mean to open help. Those phrases stay on the product screens. This article is the public version of why the envelope-admin card went empty after status flipped.

What completed means

  • Status is completed. Every required signer finished. Inkpacket stamped values onto the PDF.
  • The token is dead for more signing. Opening it does not collect another mark.
  • Reminders stop. A scheduled nudge will not go out after completion.
  • Envelope admin hides void, correct, and resend. Those verbs are for SENT envelopes.

Download the signed copy from the same envelope. Preview the pages in the field editor. If Drive archive is on in Settings, the completed PDF and a JSON audit export go to the chosen folder — or the desk reports Drive not configured when credentials are missing. The audit log on that document should show created, sent, viewed, signed, and completed. If you set a workspace or per-packet webhook, your app receives a signed POST for those events. Treat completed as a close, not as “nudge them again on this URL.”

What you cannot do

  • Void it to “clean up.” Completed envelopes return Completed envelopes cannot be changed.
  • Correct the recipient on this id. The outstanding inbox is finished on this envelope.
  • Resend the same token. There is no live signing URL left to share.
  • Un-complete from Settings. Cadence defaults apply to the next send, not this row.

If the filed copy is the wrong document, send a new envelope from the right PDF or template. Count it. Do not open checkout hoping a paid lane will unlock Void on a completed row. Billing is published, not charging. Expired is a different close — the window ended; nobody finished. Declined is the signer’s refusal. Voided is a sender stop while it was still sent. Completed is the fourth finish, and it is the one that files the PDF.

Partial, then complete

One signature on a multi-signer envelope is not completion. Status stays sent until everyone required finishes. From there you can still void, or an outstanding signer can still decline. After the last mark, those verbs are gone. That is not an un-sign of the people who already marked — void after a partial sign versus decline is the in-flight fork. Completed-lock is what happens when you miss that fork and the last person submits.

A webhook can fire completed on that same envelope id. Drive archive waits for this status — it does not upload on send. Stripe off: Payments not live. A payment request does not unlock envelope admin after complete. Text-message (SMS) is coming soon. None of those flags rewrite the stamped file.

The click-path

  1. Open the document. If status is completed, do not hunt for Void envelope.
  2. Download the stamped PDF. Read the audit. That is the record.
  3. If the work was the wrong file, send a new envelope. Keep this one on file.
  4. If someone still thinks the link is live, tell them out of band. Completed does not email a “you are done” cancel.
  5. On a phone, Documents is a drawer row. Envelope admin is on that document, not a Billing unlock.

Ask Inkpacket for completed envelopes cannot be changed to open this article. Ask what does completed envelopes cannot be changed mean to open help. Marketing Ask stays site Q&A and deep links. It will not void, correct, or resend a completed envelope from this article.

Caps and what is not open yet

Completion is not a send. The send that created the envelope already counted. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not unlock void on a completed envelope or stamp a second PDF. The FAQ and More on voiding, correcting and resending use Completed envelopes cannot be changed in the same words.

File the stamped copy. Send a new envelope when the work was the wrong file. Open a workspace on Free — see published pricing — and finish one throwaway so completed-lock honesty is a missing Void button you have already looked for, not an edit you hoped Settings would undo.

Open a workspace on Free

Billing is published, not charging. Send an envelope from the desk without a card.

Open a workspace