IpInkpacket

FAQ

Straight answers about the desk

What ships today, what stays out of scope, and how a workspace runs before Stripe or Resend keys are in place. Ask Inkpacket (bottom right) for the same answers, or to open a page.

Is Inkpacket original software?

Yes. Inkpacket is written in Next.js and Prisma, with our own envelope, field, and audit models.

Can more than one company share an install?

Yes. Every document, signer, invite, audit event, and template is scoped to an organization. Members of workspace A cannot read workspace B.

Can we reuse a PDF instead of placing fields every time?

Yes. Save a template from the desk at /desk/templates/new: upload a PDF, place the fields once (type, page, position, size, label, required, recipient slot, and select options), then start a new envelope from /desk/templates. Use template copies that layout into a draft — unlike Documents → new, which uploads a PDF with no marks. Saving a template does not count toward the monthly packet limit; sending the draft does. Templates stay inside the workspace. After you sign in, open Templates or Desk help (/desk/help#templates).

Can we remind signers and expire old links?

Yes. On send you set a reminder interval and an expiration, or keep the workspace defaults (3 days and 14 days). Set those on Documents → new (#reminders, #expiration), or change defaults in Settings #cadence. A scheduled job emails reminders when Resend is configured; otherwise it logs them — the envelope stays SENT, so copy the signing link. If Resend rejects the recipient, the reminder is logged the same way. Text-message (SMS) reminders are coming soon, and reminders go out by email today. After expiry the desk shows expired status and the signer cannot complete the envelope. Expired is not voided. Ask for a new envelope if the work still needs a signature. Desk help: /desk/help#reminders and /desk/help#expiration.

Can we text a signing link?

Coming soon. SMS signing invites are coming soon. Inkpacket does not text a signing link.

Can we collect a payment inside an envelope?

Coming soon. In-envelope payments are coming soon. Inkpacket does not collect a payment while someone signs.

Can we archive completed envelopes to Google Drive?

Coming soon. Google Drive archive is coming soon. Completed packets stay on the desk.

Can we require an access code to open a signing link?

Yes. When you send an envelope — or start a bulk send — you can set an optional access code (4–32 characters, no spaces). Inkpacket stores only a hash. The signer must enter the code before viewing or signing the PDF. A wrong code returns That access code is incorrect with remaining attempts. After five incorrect tries the page locks for 15 minutes. Share the code separately from the signing link. If the invite email is not sent, copy the signing link from the desk. Desk help: /desk/help#access-code.

Can people fill a public web form without a desk login?

Yes. Publish a Web Form from a workspace template at /desk/forms and share the /form/SLUG link. Save the template first, place at least one field, then publish — Inkpacket generates the slug from the title. The filler enters required fields plus their name and email. Inkpacket creates an envelope and sends the signing invite. Free includes 1 published Web Form; Starter includes 3, Growth 10, Agency 25. Each submission counts toward the monthly packet cap — Free is 5 packets a month, and Starter is 20 packets a month, more than Free. You can set an optional access code, reminder days, and expiration on the form. Disable a form to stop new fills (Form closed). After you sign in, open Web Forms or Desk help (/desk/help#web-forms). This path is live and does not wait on Drive or payment keys. Text-message (SMS) is coming soon.

Can we send one template to many people at once?

Yes. Open Bulk send on the desk (/desk/bulk), choose a template, paste or upload a CSV of names and emails, map the columns, and start the job. Each unique email gets its own envelope with the same field layout and the reminder and expiration you set. Retrying a job does not send a second link to a row that already went out. Each sent row counts toward the monthly packet limit (Free 5). A row that would exceed it returns HTTP 402, ENVELOPE_LIMIT — the same send cap as a single send. A sent row means the envelope exists; if invite email was not sent, open that envelope and copy the signing link. After you sign in, open Bulk send or Desk help (/desk/help#bulk-send).

Can we embed the signer on a page we already operate?

Yes. After you send an envelope, the desk copies Embed URL next to the signing link (How to embed this envelope). Iframe /embed/sign/TOKEN — or /sign/TOKEN. Signing surfaces send Content-Security-Policy frame-ancestors for inkpacket.com plus any extra origins in EMBED_ALLOWED_ORIGINS. X-Frame-Options is omitted on those routes so more than one host can frame them. The iframe posts viewed, signed, and completed messages to the parent. POST /api/v1/packets/:id/send returns embedUrl. This path is live and does not wait on Drive or payment keys. Text-message (SMS) is coming soon — live card checkout is not part of this path. After you sign in, open a draft on Documents → new (embed after send) or Desk help (/desk/help#embed). Desk help has the snippet.

Can we create envelopes from our own systems?

Yes. Owners and admins mint org-scoped API tokens in Settings (/desk/settings#tokens) and send them as Authorization: Bearer ip_… to /api/v1/packets. Create from a template, fill fields, and send. Retries can send an Idempotency-Key. Tokens stay inside the workspace. After you sign in, open API tokens or Desk help (/desk/help#api).

Will Inkpacket notify our app when someone signs?

Yes. Set a workspace webhook URL in Settings, or a per-packet URL on create or send. Inkpacket POSTs a signed JSON body on sent, viewed, signed, completed, expired, declined, voided, and corrected. The first POST is immediate. Failed deliveries retry on the hourly envelope job, up to 5 attempts, then the row is marked failed. Settings shows the last 12 deliveries with status, attempt count, and last error. Send test event posts a signed webhook.test payload so you can prove the signature. Desk help (/desk/help#webhooks) documents the signature header.

Can we void, correct, or resend an envelope after it goes out?

Yes. On a sent envelope open /desk/documents/:id — Void envelope, Correct recipient, and Resend signing email sit on Envelope admin. Void stops signing links (This signing link was voided.), correct updates the recipient on the same envelope, and resend emails the existing signing link without creating a second envelope. If Resend is not configured, resend still shows the link and says Invite email was not sent. Signers can decline with a reason (required, 500 characters or fewer); the reason is shown on that document, the sender is notified, and the envelope status becomes declined. Completed envelopes cannot be voided. Expired or declined envelopes cannot be voided, corrected, or resent. Desk help: /desk/help#envelope-admin.

How many seats does each plan include?

Published planning numbers: Free 1, Starter 3, Growth 10, Agency 50. Those are list figures on Pricing, not a live invite gate — an invite does not refuse when a workspace is full. Monthly packets and published Web Forms remain the enforced caps. Owner and admin invite a teammate from Team (/desk/team#invite). Open Pricing, Desk help (/desk/help#team), or Team.

Which plan should we pick — does paid mean more packets?

Yes. New workspaces get a 30-day free trial, no card, with Growth limits (100 packets a month and 10 published Web Forms), then Free. Free includes 5 packets a month and 1 published Web Form. Starter is $29 per month with 20 packets a month — more than Free — plus 3 published Web Forms. Growth is 100 packets a month and 10 Web Forms; Agency is 500 packets a month and 25. Each paid lane lists more packets than Free. Seat counts are a separate question: ask how many seats. Paid plans aren't open for purchase yet. After the trial, workspaces stay on Free. Open Pricing or Desk help (/desk/help#billing).

What happens if we do not have Stripe or Resend keys yet?

The product still runs. Paid plans aren't open for purchase yet. New workspaces get a 30-day free trial, no card, then stay on Free (5 packets a month). Send, bulk send, Web Form fills, and the public API share that monthly packet cap. Each API token allows 120 requests per minute per token (HTTP 429 and Retry-After). Hitting the cap returns HTTP 402. In-envelope payments are coming soon. Outbound email is logged instead of sent. When Resend is not configured the desk says Invite email was not sent — copy the link and share it. Settings shows emailConfigured. SMS signing invites are coming soon. Google Drive archive is coming soon. Embedded signing still copies Embed URL and does not wait on those keys. You can copy the signing link and the embed URL from the desk. Soft-fail help: /desk/help#invite-email, /desk/help#sms, /desk/help#drive, /desk/help#payments, /desk/help#billing.

Where are PDFs stored?

Behind an S3-compatible storage interface. Settings shows S3-compatible when S3_BUCKET, S3_ACCESS_KEY_ID, and S3_SECRET_ACCESS_KEY are set; otherwise Local fallback — development files land on the local filesystem, and uploads still work. GET /api/v1/health reports storage.configured and storage.backend. Empty uploads return Upload a PDF file. Unreadable bytes return This file could not be read as a PDF. A missing object returns The PDF could not be loaded from storage. A zero-byte stored object returns The stored PDF is empty. An unreachable bucket returns File storage is unavailable. Preview and download live on the envelope. Desk help covers the recovery path at /desk/help#files.

Can more than one person sign the same envelope?

Yes. Add recipients on the send form. Sequential routing emails the next order when everyone at the current order finishes; the same order number signs in parallel. Parallel routing invites everyone at once. Assign fields to a recipient slot. One decline still closes the whole envelope. Desk help: /desk/help#routing.

What field types can we place?

Signature, date, text, initials, checkbox, and select. Select needs at least two options. Suggest starting layout places a signature, initials, and date per recipient on the last page — it does not read the PDF or guess labels with a model. Desk help: /desk/help#fields.

Does this include notary, KBA, or qualified electronic signatures?

Not in this foundation. Those stay out of scope so the desk can stay simple: PDF, fields, link, signature, audit, download.

What is the product domain?

inkpacket.com. From lines and public links should use that host in production.

Ready to send a packet?

Open a free workspace. No card. 30-day free trial, no card. Paid plans aren't open for purchase yet.

Open a workspace