Thank you for all your feedback and voting on this feature.
We recently had a Product Roadmap update, and there has now been an item added to the Roadmap :
EDIT: The target date of release supporting Multiple Custom Domains per tenant has been changed, currently the estimated time is set to Q4 2025 (OCT-DEC).
Support Multiple Custom Domains per tenant - Target release in Q3 2024 (Aug-Oct). (Please note that the target dates may be subject to change). We do not have any further details at this time.
Although the release date is quite far out, it is great to see that our product team has added this feature to the future plans. Thanks again for all the feedback that helped get this feature on the roadmap.
EDIT: The target date of release supporting Multiple Custom Domains per tenant has been changed, currently the estimated time is set to Q4 2025 (OCT-DEC).
The current description mentions about the ability to create more than one customized login experience within a single tenant which can be catered towards different applications or Organizations. Although currently no mention for branding by each custom domain. We may have more details in the future or you can look to raise an additional feedback post for this specific use case, thanks!
Hi all! My name is Carolyn, and I’m the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences.
We’re conducting 45-minute interviews. These sessions will be conducted via our user research platform Great Question , and they will be recorded for internal purposes only. As a token of appreciation for your time and feedback, we’re offering a $60 incentive.
If you’re interested, please complete the screener to see if you are eligible to participate here. Feel free to follow up with me if you have any questions!
Hi Oleh! My name is Carolyn, and I’m the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences. My team thinks you would be a great candidate for the study.
We’re conducting 45-minute interviews with a $60 incentive through our tool GreatQuestion. If you’re interested, please complete the screener to see if you are eligible to participate here. We will reach out to you within 48 hours to schedule an interview. Feel free to follow up with me if you have any questions!
Hi Vaclav! My name is Carolyn, and I’m the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences. My team thinks you would be a great candidate for the study.
We’re conducting 45-minute interviews with a $60 incentive through our tool GreatQuestion. If you’re interested, please complete the screener to see if you are eligible to participate here. We will reach out to you within 48 hours to schedule an interview. Feel free to follow up with me if you have any questions!
Hello everyone, I’ve been trying to address this issue through direct channels with Auth0. While Sales has been unresponsive, the development team provided some solutions. The product team has this feature in the backlog, but details are limited. To expedite, we need more visibility. Please upvote the ticket and reach out to sales for support. Thank you.
Just came to vote on this as it would be extremely helpful to allow us to change the custom domain with a staged approach without breaking all of our customer’s SSO connections that use our custom domain in their callback URL. As an enterprise customer, the timeframe update is very disappointing.
This is incredibly important if you need to change your domain name as well. You will otherwise lock users out. Any customers of yours with SSO configured will need to update their configuration and so on. It may not be so easy to update mobile apps where now someone is using an older version that has an old custom domain configuration. Links for email verification, password reset, etc. they all break.
Like others have said this isn’t just a convenience, this is a mandatory feature. In the very least a way to migrate from one to another so you don’t have service interruption. There are simply times when a domain must change (legal reasons, etc.) and to have a service interruption here, you’re honestly breaking your SLA. Not really sure what the mandatory support charges are that came into effect either, but boy what are we getting for that?
Very unfortunate to see this slated for Q4 2025 after all this time.
:
and wanted to reiterate that the timelines for feature requests are subject to potential changes.