When workspace invite email soft-fails

A workspace invite is a seat, not a signing link. Owner or admin opens Team, enters an email plus Member or Admin, and A team invite creates the row. The route returns inviteUrl, emailSent, and emailError. When RESEND_API_KEY is missing — or Resend rejects the recipient — Team shows Invite email was not sent — copy the link and share it. The invite still exists. That is a seat-invite soft-fail.

It is not a seat-cap refusal. Published seat counts are planning numbers; invite does not refuse when a workspace is full. There is no HTTP 402 on this route. It is also not a signing-invite skip, even though the sentence looks the same. Signing invites live on an envelope. This one lives on Team.

Desk help is Docs and Docs. Seat planning is planning team seats on Inkpacket. Pricing lists Free 1, Starter 3, Growth 10, Agency 50 published seats (planning).

What still happened

• The invite row exists. Open /desk/team#invites.
• inviteUrl is on the response and on the desk.
• emailSent is false when mail did not go out.
• Members still cannot invite. Only owner and admin can.

Copy the URL. Share it on a second channel. Do not create a second invite because the first email never arrived — that is a second outstanding row for the same person, not a retry. Do not open Billing to “unlock mail.” Checkout is not open and does not configure Resend.

Same sentence, different object

Signing send says Signing link is ready. Invite email was not sent — copy the link and share it. A Web Form fill says The invite email was not sent. Use the signing link below. Team says the same honesty about a seat URL. Copy the object in front of you. A teammate who opens a signing URL cannot join the workspace. A signer who opens an invite URL cannot finish an envelope.

GET /api/v1/health reports emailConfigured. Settings #email shows the same flag. When the flag is false, every outbound path logs instead of sending: first invite, reminder, decline notice, seat invite. The desk does not pretend mail was delivered. Text-message reminders are coming soon is a different skip — Text-message (SMS) is coming soon.

What you should not do

• Do not treat the skip as a full workspace. The person is not a member until they accept.
• Do not expect invite to refuse at the published seat number. It will not.
• Do not POST invite again to “retry email” unless you meant a second row.
• Do not revoke an API token because a teammate never got mail. Tokens are a different secret.

If they never received the URL, paste it. If they accepted and still cannot send, they may be a member who lacks owner or admin — members send envelopes and cannot invite. If they landed on the wrong organization, they signed up into a different workspace. Invite does not merge tenants.

The click-path

1. Open Team at /desk/team. On a phone, Team is in the desk menu.
2. Create an invite at /desk/team#invite — email plus Member or Admin.
3. If Team shows Invite email was not sent, copy inviteUrl immediately.
4. Share that URL on a second channel. Do not mint a twin invite to retry mail.
5. When they accept, they can send. Members still cannot invite.

Ask Inkpacket for how to invite a teammate to open help. Ask invite teammate to open the form. Those phrases stay on the product screens. This article is the public version of the skip, not a promise that Resend is configured.

Over the planning number

A team invite creates the invite even when the workspace is over the published seat count. Free’s 1, Starter’s 3, Growth’s 10, and Agency’s 50 are planning numbers on Pricing. Monthly envelopes and published Web Forms remain the live gates. A teammate who accepts can send until the envelope cap fires — HTTP 402 ENVELOPE_LIMIT — not until a seat HTTP status that does not exist.

Caps and what is not open yet

A seat invite is not a send. The envelopes that teammate later issues will count. 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. None of those flags create the teammate’s mailbox. The FAQ and FAQ use Invite email was not sent in the same words.

Create the invite. Copy the URL when mail skips. Stay on that row. Then let them send on Free — see published pricing — after they accept. Open a workspace if you still need the first owner seat, or sign in and practice a throwaway invite so the soft-fail is something you have seen.