Experience Cloud Developer Guide

Get Up to Speed with Experience Builder Sites
Develop Experience Builder Sites: The Basics
Using the Developer Console
Configure Drag-and-Drop Aura Components for Experience Builder
Expose Component Attributes in Experience Builder
Tips and Considerations for Configuring Aura Components for Experience Builder
Supported Aura Components, Interfaces, and Events
Personalization Target Developer and Group Names
Comply with a User’s Personal Information Visibility Settings
Customize the Look and Feel of an Experience Builder Template
Develop Secure Sites: Authenticated and Guest Users
Develop Secure Sites: Lightning Locker and CSP
Analyze and Improve Experience Builder Site Performance
Add Pardot Tracking to Your Experience Builder Site
Use a CMS with Your Experience Builder Site
Report on Deflections: The Deflection Signals Framework
Deploy an Experience Cloud Site from Sandbox to Production
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Comply with a User’s Personal Information Visibility Settings

Orgs with portals and sites provide specific settings to hide a user’s personally identifiable and contact information from other users. These settings aren’t enforced in Apex, even with Apex security features such as the WITH SECURITY_ENFORCED clause or the stripInaccessible method. To hide specific fields from a guest or external authenticated users, follow the sample code outlined below.

To hide a user’s personal information in the User object:

To comply with a user’s contact information visibility settings within a community or portal, we check the preferences associated with specific fields and show or hide the data accordingly. For a user’s contact visibility settings within an Experience Cloud site: