When implementing an Experience Cloud site accessible by external and unauthenticated guest users, keep these security considerations in mind. External users have login privileges to your Experience Cloud site, but they can’t access your internal Salesforce org. A guest user is anyone on the internet who can visit the publicly accessible pages and components of your Experience Cloud site.
Granting permission to view an object allows external users to view that object using standard controllers. Standard controllers are available in Experience Builder sites and Salesforce Tabs + Visualforce sites that have Lightning features enabled. These controllers grant access based solely on the platform declarative permissions.
For every use case, determine whether to implement a custom access control model or to rely on the declarative platform access control model. We recommend using the platform declarative access control model when possible. However, sometimes your requirements call for a custom access control model.
Allow guest and external users access to only those classes that they must call.
If guest or external users must run flows, override the flow permission to grant access only to specific external user profiles, permission sets, or site guest user profiles, rather than allowing users to run all flows. Avoid running flows in system context when possible, and restrict access to subflows. Otherwise, ensure that you implement procedural access controls for those flows and subflows.
Sanitize user-controlled data passed into dynamic SOQL queries.
j
