What the audit log records

The audit log on an Inkpacket envelope records created, sent, viewed, signed, completed, and — when they happen — declined, voided, corrected, and expired. Those events are scoped to the organization. That is audit-record honesty: the desk log is the record, Drive’s JSON export is a copy after complete, and the trail does not store PIN attempts, the plaintext access code, SMS bodies, or card numbers.

How to read each verb is how to read an Inkpacket audit trail. The stamped file is what a completed envelope includes. The POST that leaves the desk is listen for envelope status webhooks. Desk help is Docs. This guide is the include/exclude list.

The FAQ says the trail stays readable on the envelope. Features lists the filed copy under completed PDF. Ask Inkpacket for audit log what gets recorded to open this article. Ask how to void an envelope to open help. Ask webhook settings to open Settings. Those phrases stay on the product screens. This article is the public version of what will not be on the printout.

What is written

• Created — a draft exists. Nothing invited yet.
• Sent — a signing link was issued. If Resend is missing, the invite was logged and the desk still shows the URL.
• Viewed — someone opened the token (and passed an access code if you set one). Viewed is not signed.
• Signed — that signer submitted required marks. Others may still owe a mark.
• Completed — every signer finished. The stamped PDF exists.
• Declined, voided, corrected, expired — when those closes happen. One decline closes the whole envelope.

A Web Form fill creates an envelope and then sends. The trail starts when that envelope exists, not when the stranger opened /form/SLUG. A bulk job creates one envelope per unique email — read each envelope, not the job row, when you need viewed or signed. Sequential send records the first order before a later signer has a token. That is expected.

What is not written

• PIN tries, remaining-attempt counts, or the plaintext access code. Inkpacket stores only a hash.
• Field values as a second table. Marks land on the stamped PDF. The log says signed, not what they typed.
• Card data. Stripe off: Payments not live. Checkout is not open. Nothing to store.
• Text-message (SMS) is coming soon. Drive bytes log Drive not configured when keys are missing.
• Webhook delivery rows. Settings shows the last 12 deliveries. That log is not the envelope audit.

Viewed does not prove they read every page. Signed does not prove they understood a clause. Completed does not prove the PDF was the right file — only that the file you sent received marks. If the paper was wrong, send a new envelope. Envelope admin will not rewrite a filed copy. Do not treat iframe postMessage as the legal record. The parent tab can lie.

Copies that are not the log

When Drive archive is on and credentials are set, a completed envelope uploads the stamped PDF and a JSON audit export to the chosen folder. Without keys the desk reports Drive not configured and does not pretend the upload happened. That JSON is a copy of this log, not extra events. When Drive archive soft-fails is that skip.

A workspace or per-packet webhook POSTs the same lifecycle: envelope.sent, envelope.viewed, envelope.signed, envelope.completed, envelope.expired, envelope.declined, envelope.voided, envelope.corrected. Verify HMAC-SHA256 of timestamp.body. A 200 on an unverified body is not an envelope status you can file. Envelope send still succeeds if the webhook fails. Do not send a twin envelope to “retry the webhook.”

The click-path

1. Open the document on the desk. Read the events in time order. Status is the latest close.
2. If someone asks whether mail went out, sent plus the copy box beats a guess. Invite email was not sent still leaves a URL.
3. If they ask what the signer typed, open the stamped PDF — not this list.
4. If they ask whether your app heard completed, check Settings deliveries or your verify, not a second envelope.
5. Do not void a completed envelope to “clean the log.” Completed envelopes cannot be changed.

Ask Inkpacket for audit log what gets recorded to open this article. Ask how to decline to open help. Marketing Ask stays site Q&A and deep links. It will not invent an event that is not on the envelope.

Caps and what is not open yet

Reading the log 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 add PIN tries to the trail or invent a notary event. The FAQ and completed PDF on Features keep the same created-through-expired list.

Read the events that exist. Do not ask the log for secrets it never stored. File the stamped PDF when completed is there. Open a workspace on Free — see published pricing — and send one throwaway so audit-record honesty is a short list you have already pointed at before someone asks where the PIN guesses went.