Skip to main content

Hi everyone,

I have a Salesforce sandbox where I need to have 3 different users using the same email address.

I’m facing an issue when trying to update the email addresses of these users.

For example, one user currently has:

sim.taylor@xyz.com.invalid

I changed it to:

testuat@xyz.com

After saving, Salesforce sends a verification email to the new email address. The user clicks the verification link and completes the verification successfully.

However, when I go back to the User record in Setup, the email address still shows:

sim.taylor@xyz.com.invalid

It seems like the email change is not being saved even though the user has successfully verified the new email address.

Has anyone experienced this issue in a Salesforce sandbox, particularly with the .invalid email addresses?

What is the correct process for updating the email address so that it remains as the new email after verification?

Also, is there any limitation or recommended approach for having multiple Salesforce users with the same email address in the same sandbox?

Thanks in advance! 

 

#Salesforce Admin  #Salesforce Developer  #Salesforce  #Security

5 个回答
  1. 昨天,16:29

    Hi Sans, 

     

    This looks like a known issue tied to a recent release, not something wrong with your setup. Salesforce has an open issue where changing a user's email post Summer '26 causes the verification link to redirect to the login page instead of completing the change, and the email address stays unchanged even after the user clicks "Verify Email Address." 

    Official reference:

    https://help.salesforce.com/s/issue?language=en_US&id=a02Ka00000mGGGyIAO

     

     

    Workarounds from that same official issue page, in order of ease: 

     

    1. Edit the user record, remove the ".invalid" suffix or enter the new email address, and while still in edit mode, check "Generate new password and notify user immediately." This sends a reset email that lets the user verify the email and set a password in one step. 

     

    2. If the user gets redirected to login and is then prompted for a verification code sent to the OLD email, have them enter that code, this completes the update even though the "click the link" flow appears broken. 

     

    3. If the user can log in via SSO, have them establish a session via SSO first, then click the verification link. 

     

    4. If none of the above work, an admin can set a temporary password using System.setPassword() for that user, then reattempt the email change. 

     

    5. As a last resort, set Trusted IP Ranges for the org, or add a phone number to the user's record. Both have resolved this for others per the same article. 

     

    Separately, on your question about the ".invalid" suffix: this is expected sandbox behavior, not a bug. Every sandbox refresh or clone automatically appends ".invalid" to all User email addresses so production users never receive automated emails from sandbox testing. You have to manually remove ".invalid" per user if you want that sandbox user to send/receive real emails. 

    Official reference:

    https://help.salesforce.com/s/articleView?id=Sandbox-email-addresses-appended-with-invalid-on-User-records-post-refresh&language=en_US&type=1

     

     

    On your last question, multiple users with the same email address: Salesforce does not enforce email uniqueness the way it enforces Username uniqueness. Username must be globally unique across all of Salesforce, Email does not have that same platform-level restriction. 

    Official reference (Trailhead, Salesforce-authored):

    https://trailhead.salesforce.com/content/learn/modules/lex_implementation_user_setup_mgmt/lex_implementation_user_setup_mgmt_adding_users-hoc

     

     

    So 3 users sharing one email address is technically possible, but keep in mind: whichever user's "Email" field matches will all receive password reset emails, report subscriptions, and notification emails to that same inbox, so this is only advisable for non-production/test scenarios, exactly what you're doing in this sandbox.

0/9000