Thanks Nik for the thoughtful and detailed response and possible workaround!
I may pivot to that implantation flow in the future.
I did end up going with another route, simply because it was implemented and released just before your response.
This way still requires “Both” being used for the Client’s Login XP settings.
I created custom K:Vs in the user’s app_metadata : created_org_id & created_org_name
Then my React app will guide the user into their organizational context in both of these circumstances:
- new registration, completed Form workflow
- accidentally selects “personal account” from the org picker
I also created a new Feature request post for a “pre-login” trigger that can be activated regardless of personal vs org context in regards to the client’s login XP setting. As well as the ability to render a form.