Team invite flow

Step 1 — Send

Owner enters an email. The server creates a time-limited invite record, stores a hashed token, and sends a magic link. The UI shows a pending row immediately — optimistic, no spinner.

Step 2 — Accept

Recipient clicks the link. The page reads the token from the URL, validates it server-side, and either joins them to the team or surfaces a reason it failed.

Step 3 — Errors

Expired, already-used, and invalid tokens each get a dedicated inline message. No redirects — the page stays put so the user can copy the link or request a new one.

• •Expired — “This invite link has expired. Ask the team owner to send a new one.”
• •Already used — “This invite was already accepted. You’re all set.”
• •Invalid — “We couldn’t find that invite. Double-check the link.”