# Auth0: B2B SaaS, Multi Tenant (Organizations), Self Service Signup Support

**URL:** <https://community.auth0.com/t/auth0-b2b-saas-multi-tenant-organizations-self-service-signup-support/197631>\
**Category:** Get Help\
**Tags:** signup-prompt-new-experience, login-experience\
**Created:** [February 24, 2026, 11:00pm UTC](https://community.auth0.com/t/auth0-b2b-saas-multi-tenant-organizations-self-service-signup-support/197631 "2026-02-24T23:00:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![swezey-subtrack](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swezey-subtrack/32/70799_2.png) [@swezey-subtrack](https://community.auth0.com/u/swezey-subtrack)\
**Post date:** [February 28, 2026, 6:59pm UTC](https://community.auth0.com/t/auth0-b2b-saas-multi-tenant-organizations-self-service-signup-support/197631/4 "2026-02-28T18:59:24Z")

</div>

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:

1. new registration, completed Form workflow
2. 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.

> [@Pre-Login Trigger: Ability to activate a Form before the post-login trigger](https://community.auth0.com/t/pre-login-trigger-ability-to-activate-a-form-before-the-post-login-trigger/197742):
>
> Feature: a new “pre-login” trigger that can also render a form Activates synchronously before post-login, but after the user is registered. Works regardless of the login experience settings in the application’s configuration. Description: Having Auth0’s Form rendered before a user is “fully authenticated” would be beneficial in many use cases involving new users & self-service registration support. Even more so for the B2B, multi-tenant cases. Use-case: Concrete example: React App: Login …

---

_[View the full topic](https://community.auth0.com/t/auth0-b2b-saas-multi-tenant-organizations-self-service-signup-support/197631)._