The Salesforce Help & Training Portal uses a user's email address as a unique identifier to associate cases with a specific user.
When a user's email address is updated on their Salesforce User record, previously submitted cases (created with the old email address) may no longer appear in that user's Help Portal view.
These cases are not deleted. They remain accessible to users who have permission to view all cases within the organization, such as through My Org's Open Cases and My Org's Closed Cases.
This article explains what to do if a user loses access to previously submitted support cases after their Salesforce User email address is changed.
The Salesforce Help & Training Portal uses a user's email address as the unique identifier that links a user to their submitted cases. When a System Administrator updates a user's email address on their Salesforce User record, cases created under the old email address may no longer appear in that user's Help Portal view. The cases are not deleted or lost - they simply are not automatically re-linked to the new email address.
If a user loses access to previously submitted cases after an email address change, follow these steps:
Salesforce Support can help re-associate the cases so they are visible under the updated email address.
For example, if a support engineer's email address changes from jsmith@acme.com to jane.smith@acme.com, any cases they submitted under the old address will no longer show up in their Help Portal case list. A System Administrator at Acme can log a new case with Salesforce Support, listing both email addresses and a couple of the missing case numbers, so Support can re-link the cases to the new address.
Even before Support re-associates the cases, they remain visible to users who have permission to view all cases within the organization, such as through:
000395471

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.