Customer Portal users who access the 'My Cases' list view in the Salesforce Customer Portal see a filtered set of cases based on their relationship to those cases, not based on case ownership.
Case visibility in the Customer Portal is controlled by the Contact Name field on the Case, not by the Case Owner field. Understanding this distinction is essential for correct list view configuration.
If the Customer Portal user is the Contact on the Case, they have the ability to see it. When a portal user selects the 'My Cases' list view, Salesforce returns cases where they are listed as the Case Contact — not cases where they are the Case Owner. This is by design, because in most scenarios a customer who logs a case is never the Case Owner, but almost always the Case Contact that an internal Case Owner reaches out to.
To ensure that the 'My Cases' list view works correctly for community users, the following configuration must be in place:
For self-service community templates, the list view API still filters by caseownerid = currentUserId rather than by Case Contact. This means the 'My Cases' list view behavior differs for self-service community template users. Note that self-service community templates are in phased retirement and can no longer be used when creating new communities.
For self-service community templates, or when custom filtering by contact is needed, create a custom formula checkbox field where ContactId = $User.ContactId and use this field as the filter criteria in the list view. This ensures the list view returns the correct cases for the logged-in portal user.
000384975

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.