Accept an invitation
What It Does
Acceptance proves possession of an existing offer and cannot select a different person or privilege set. The password and provider-link paths both prepare external identity effects before database activation.
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
Single-use applies to conditional database consumption. It does not serialize provider passwords across concurrent acceptances. That race is a finding requiring a test and a product decision rather than a promise of safe retry.
Conditional consumption admits one database acceptance winner; an already accepted token for an active member returns the prior success. Provider enabling and password setting occur before this transaction and can be repeated or raced. Link-session consumption is also conditional; neither database condition proves atomic external-provider effects.
Acceptance re-evaluates inviter authority before activation and commits token consumption, membership activation and pending grants together. Two password requests can both reach the provider before one loses database consumption; the credential race remains unresolved.
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.