Register, confirm and sign in a portal member
What It Does
Portal self-registration requires an active registered pool and mailbox confirmation. Confirmation creates membership through the trigger; password sign-in repairs a confirmed account when that trigger failed.
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
Workspace availability and missing-pool errors are not identical in the implementation. Their documented disclosure and response-status disagreements remain findings. Sign-out affects sessions without promising immediate invalidation of an already issued access token.
Repeated confirmation or sign-in repair converges on the existing member, identity and Portal Member assignment. A failed confirmation trigger can leave the provider account confirmed, and successful password sign-in invokes the same missing-member repair.
Membership, identity, assignment and activation history commit together in their provisioning transaction. Address uniqueness is per workspace portal; provider confirmation remains a separate external action.
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.