PUBLIC-SECTOR-SOLUTIONS-2025 practice question 25 of 35

A public sector organization (PSO) is implementing Public Sector Solutions. As part of this implementation, the PSO is deploying a new site to…

Full set: 100 questions

Domain Application and Case Management

A public sector organization (PSO) is implementing Public Sector Solutions. As part of this implementation, the PSO is deploying a new site to provide constituents with information about the service they provide. Constituents will be able to register and log into this new site to access some features as well. The PSO needs to ensure that constituents are unable to see each other by default for all sites that they configure. What can the Technical Consultant configure to meet this requirement for the PSO?
Answer options
A: Disable the user sharing in the site administration settings page
B: Uncheck the 'Site User Visibility' checkbox in the sharing settings page Correct answer
C: Set the Organization Wide Default for the User Object to "Public Read Only"
D: Remove access to the user object from the Permission Set assigned to the external users
Correct Answer:
B. Uncheck the 'Site User Visibility' checkbox in the sharing settings page
Explanation

The 'Site User Visibility' setting, located in the main Sharing Settings page (Setup > Sharing Settings), is the master switch that controls whether users with customer or partner profiles in an Experience Cloud site can see other users in the same site. By unchecking this box, the organization-wide default for external users is set to private. This ensures that, by default, constituents in any site within the org cannot see each other, directly fulfilling the Public Sector Organization's privacy requirement for all configured sites.

Why Incorrect

A. Disable the user sharing in the site administration settings page: This setting is configured per site in Experience Workspaces and would not establish a default for all sites as required by the scenario.
C. Set the Organization Wide Default for the User Object to "Public Read Only": The Organization-Wide Default (OWD) for the User object controls visibility for internal users, not the visibility between external (site) users.
D. Remove access to the user object from the Permission Set assigned to the external users: This would prevent users from seeing even their own user record, which is necessary for basic profile management and site functionality.

References

1. Salesforce Help Documentation, "Control Who Experience Cloud Site Users Can See": This document explicitly states, "To control visibility for external users, use the Site User Visibility setting on the Sharing Settings page in Setup. When this setting is enabled, you can control visibility on a site-by-site basis... If this setting is disabled, external users are private and can’t see other users." This confirms that disabling the setting at the org level is the correct approach for a default.

2. Salesforce Security Guide, "External Organization-Wide Defaults" section: This guide details that external OWDs control the baseline access for external users. It clarifies that for the User object, visibility for external users is not controlled by the standard OWD but by the specific 'Site User Visibility' checkbox in Sharing Settings.

3. Salesforce Developer Documentation, "UserVisibility (ConnectApi)": The API documentation for user visibility in Experience Cloud sites references the organizational preference doesSiteUserVisibilitySeeEachOther which corresponds directly to the 'Site User Visibility' setting, reinforcing its role as the org-level control.

Scroll to Top