Invite a person and deliver the invitation
What It Does
Invitation persists the offer before any provider or sender call. The hop rows separate delegated authority, database creation, sign-in account preparation, token issuance and message delivery.
The Flow
The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.
When Something Fails
Delivery failure does not undo the invitation. Issuance can precede policy withholding or failed sending, and concurrent delivery order does not identify the valid link. The recorded finding asks for race proof and a clear retry experience.
Preparation finds an existing recorded or named provider account before creating one. Resend replaces the invitation; token validity follows the current invitation and digest, not the last e-mail delivered. Active memberships use role management, invited memberships use resend and revoked memberships reuse their retained row for a new offer.
Membership, invitation, pending grants and database history commit together. Uniqueness prevents duplicate outstanding invitations within the membership boundary. Provider and e-mail work run after the transaction.
Open Design Questions
The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.