You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have added a new verified domain added, let us call it Domain2.com and have renamed most users accounts from user@domain1.com to user@domain2.com. Some are still trying to use their old accounts to log in therefore new duplicate accounts are being created: user@domain1.com.
We want to prevent @domain1.com accounts from being created, but still, allow existing @domain1.com accounts to work until we change them.
Can Domain1.com be removed from Approved domains under Site Access, without affecting Domain1.com users?
Hi Sham,
Have you already implemented Atlassian Access? Or just preparing for it?
Prior to having Atlassian Access we were able to remove an approved domain with no impacts on the users.
This is correct. Removing an approved domain will simply prevent new users on @domain1.com from joining the site, it won't have impact on any existing users. I think this is what you want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a late reply.
Thanks John and Dave - it can be removed with no impact - confirmed
Not implementing Atlassian Access.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.