Loading

Salesforce Email-to-Case and Organization-Wide Email Address Verification Link Fails When a Different Admin Clicks It

Udgivelsesdato: Oct 12, 2026
Beskrivelse

After the Summer '26 release, clicking a Salesforce Email-to-Case routing address verification link or an Organization-Wide Email Address verification link while logged in as a different admin than the one who created the address causes the verification to fail. This is Working As Designed (WAD): the verification link is intentionally session-bound to the admin who initiated it.

Symptoms include the following: clicking the verification link redirects to the Salesforce login page, Device Activation intercepts the flow after login, and the address remains unverified. The issue occurs only when a different admin clicks the link.

This behavior is a security design introduced in Summer '26, not a bug. The EmailChangeVerification service requires the same user session for both initiation (clicking "Send Verification" in Setup) and completion (clicking the verification link in the email). If a different user clicks the link, the token mismatch triggers Device Activation, which blocks the verification. This behavior affects Summer '26 and later.

Løsning

This article explains why Salesforce Email-to-Case routing address and Organization-Wide Email Address verification fails when a different admin clicks the verification link, and how to complete verification. 

Email-to-Case Routing Address: Steps to Reproduce

  1. Log in as Admin A, create a new Email-to-Case routing address, and click Send Verification.
  2. Close all Salesforce browser tabs.
  3. Open the verification email and click the link.
  4. When redirected to login, log in as Admin B (a different user).
  5. Observe that Device Activation intercepts the flow and verification fails.

Expected result: Verification completes. Actual result: Device Activation fires and verification fails.

Organization-Wide Email Address: Steps to Reproduce

  1. Log in as Admin A, go to Setup, open Organization-Wide Addresses, add a new Organization-Wide Email Address, and click Save.
  2. Close all Salesforce browser tabs.
  3. Open the verification email and click the link.
  4. When redirected to login, log in as Admin B (a different user).
  5. Observe that Device Activation intercepts the flow and verification fails.

Expected result: Verification completes successfully. Actual result: Device Activation fires and verification fails.

Email-to-Case Routing Address: Resolution and Workaround

Option 1 (Preferred): Forward the verification email to the admin who originally created the routing address. That admin logs in and clicks the link. The inbox the email arrives in does not matter. Only the logged-in identity matters.

Option 2 (A different admin needs to verify):

  1. The new admin logs into Salesforce.
  2. Go to Setup, then Email-to-Case, then Routing Addresses.
  3. Click Send Verification again. This generates a new token bound to the new admin's session.
  4. Open the new verification email and click the link while still logged in.
  5. Verification completes successfully.

Organization-Wide Email Address: Resolution and Workaround

Option 1 (Preferred): Forward the verification email to the admin who originally added the Organization-Wide Email Address. That admin logs in and clicks the link. The inbox the email arrives in does not matter. Only the logged-in identity matters.

Option 2 (A different admin needs to verify):

  1. The new admin logs into Salesforce.
  2. Go to Setup, then Organization-Wide Addresses.
  3. Click the verification link next to the unverified address (or delete and re-add it). This generates a new token bound to the new admin's session.
  4. Open the new verification email and click the link while still logged in.
  5. Verification completes successfully.
Vidensartikelnummer

005388172

 
Indlæser
Salesforce Help | Article