Restrictions to primary email changes, now generally available
Hi Community,
We're enhancing security by restricting end users from changing their primary email address in the Manage Email Addresses UI under Personal Settings → Profile. Now, only System Administrators can modify a user's primary email address via the User Management UI in the Admin Center, and this will be limited to changes within the current domain of the user’s existing primary email address. Any primary email changes to a different domain will require SysAdmins to use the user merge process, ensuring robust governance and protection of shared items.
This change will impact all plans. To learn more about how to update the primary email address, please read this help article: Add a secondary email address to your account
You can also stay informed by subscribing to receive product release updates for curated news of recently released product capabilities and enhancements for the platform of your choosing, delivered to your inbox. As new releases occur, you will receive a weekly email with news of what's released every Tuesday.
Cheers,
Lekshmi Unnithan
Senior Product Marketing Manager
Comments
-
Thanks for this update! I appreciate this added level of security for users.
Michelle Choate
michelle.choate@outlook.com
Always happy to walk through any project you need help with! Book time with me here: https://calendly.com/michelle-choate
-
I can appreciate the enhanced security, but this eliminates the one workaround I had for our regularly-changing user email addresses. My users lose access any time they have a name change or a domain change from moving to a different location, and with the number of end-users I support, that happens about once a week. Looking forward to getting a solution from our account team that deosn't require so much admin intervention.
-
Restricting primary email changes to System Administrators only helps protect user data and shared items within your platform. By limiting domain changes and requiring a more controlled process (such as the user merge process for cross-domain updates), you’re adding a robust layer of governance.
-
If I have two validated domains, I should not have to use user merge to change the primary. I can see how this would be useful if you're changing it to a domain you don't manage but when you have users with multiple emails across multiple domains, this is a headache.
-
The feature here implies I can just do a merge when the domain is different, however that doesn't work when the secondary email is already added/merged. Support informed me that:
- For users that were previously merged, you would need to remove the email and then invite the account to have the merge working properly.
I have prepared an email migration domain for months, but because of this, I'm going to have to:
- Remove everyone's secondary email
- Reinvite everyone, including people in parental leave/long term sickness (so I won't be able to finalise migration for months)
- Merge everyone
For more than 100 users.
If felt really smart adding everyone's secondary email in advance, thinking great, I'm just going to click a button and everyone's going to switch email real quick. What a waste of time.
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 64.9K Get Help
- 441 Global Discussions
- 139 Industry Talk
- 471 Announcements
- 4.9K Ideas & Feature Requests
- 129 Brandfolder
- 148 Just for fun
- 68 Community Job Board
- 495 Show & Tell
- 33 Member Spotlight
- 2 SmartStories
- 300 Events
- 36 Webinars
- 7.3K Forum Archives