Hi all,
I’m pleased to share the news that this feature has now got a General Availability Target Date - 28th June 2023
Please note that this date may be subject to change, however, its great news to see this has now got a date we are working towards.
I’m not aware of a beta offering at the moment but will report back here if I see anything.
We would be happy to participate in the beta if possible
Very much looking forward to these! Please let us know if there is anything we can do to help with the release.
Looking forward to the release of the organization prompt feature. I do have one question though.
Will this feature support Automatic User Migration?
Hi all, quick update.
The target date for this feature is still the 28th of June (as mentioned previously, this is a tentative date). I’ll provide an update on this thread if I see any changes.
There is no Beta or Early Access for this feature (but thank you for all the interest!), and our testing has already begun earlier this month.
Hi @eric.gaberik , Automatic User Migration is in our backlog and not yet on our product roadmap, this FAQ page here explains a work around - Assign Users to Organizations after auto-migration from Custom Database
Awesome news! @nathan.jenkins
A majority of users will only be a apart of one organization. Will this update show a drop-down when a user has more than one org and nothing at all when the user is only a part of one org? That way a user doesn’t have to worry about org name at all if they are only a part of one org?
Hi @justin.chitla ,
From what I understand, during the login flow, the user will only be prompted to choose an org if they are part of more than one.
So for a user with just one org this additional step will be skipped and they will log straight into the application 
Very much expecting this feature!
Same! Excited for this. I was able to implement your workaround of using silent auth after the initial login, but it’s pretty janky.
Wow, apparently I’m in luck. I was just investigating this exact situation. I’m glad the feature is coming out June 28th. Thank you!
Additional Question:
In the management API or SDK, is there (or will there be), a way to create a user in a specific organization in one step? As I understand currently, that logic has to be implemented in our app. First check if the user exists in any org. If not invite user to the App. Then assign them to an org. If there was a createUser({org_id:xxx}) that did all those steps that would help streamline as well.
Could you provide some clarity or confirmation on if June 28th is still the target release date? We pushed our launch back to have this feature and are super stoked but want to make sure we are planning correctly. Thanks!
Can it be a beta version ??
In my application I cannot see that new organization screen prompt.
Did you need to do some extra configuration ??
Hi All, The rollout of this feature update has started and may be available in your tenant environment. 
Supporting documentation will be provided once the announcement has been made on the Auth0 Changelog, please keep an eye on the changelog page to find any links to supporting docs.
To get you started and test the feature, First turn the Authentication Profile to Identifier First.
Then go to your Auth0 Application and Organization Tab, there you will need to select the Type of Users, and select the preferred Login Flow (Prompt for Organization)
Yeah, I set it up in the dashboard under Applications > {My App} > Organizations
Was easy to set up and seems to be working well for my use case! I was able to delete the silent authentication hack completely.
Ok, I spoke too soon 
It seems there is still a limitation, but maybe I’m missing something. First, let me lay out our requirements.
If I select “Business Users”, number 2 breaks. When a new user signs up they get this error.
But what I really want is for them to be signed in and prompted to create a new organization. We have this flow built out already.
If I instead select “Both”, number 3 above breaks. Users can sign in without an org and I can show them the prompt to create a new org. But then they get prompted to log in as individuals or the org, when we really only want to allow authenticating under the org:
Slack is mentioned as an example under “Business Users”, but that’s not quite true. Slack actually has the exact flow I’m interested in. If you sign up as a new user, you’re prompted to create a workspace:
If instead you sign up as a user with only one workspace membership, it logs you right into that workspace:
Sorry for the long post, just wanted to provide as much context as possible. Let me know if there’s a way to configure this flow with this new feature set, otherwise I’ll bring back the workaround where you fetch the user’s org memberships and do silent re-auth.
Hi @igillis! Good eye on the release catch.
You’re correct in your assessment of current capabilities. However, we’re scoping out what self service organization creation and sign up should look like as a future roadmap item.
I’ll send you a DM about setting up a time to chat if you’re interested.
