In Winter ’21, Salesforce is enforcing guest user security policies
introduced in the past few releases, such as the Secure guest user record access setting. Also,
Salesforce is reducing object permissions for guest users.
Secure Guest User Record Access Can’t Be Disabled
The Secure guest user record access setting was enabled in Summer ’20, but could still be disabled during that release. To safeguard your Salesforce org’s data, in Winter ’21, this setting is enabled in all orgs with communities or sites and can't be disabled. The Secure guest user record access setting enforces private org-wide defaults for guest users and requires that you use guest user sharing rules to open up record access. You also can't add guest users to groups or queues or grant guest users record access through manual sharing or Apex managed sharing.
Reduce Object Permissions for Guest Users
With the Winter ’21 release, Salesforce is disabling the View All, Modify All, edit, and delete object permissions for guest users in existing orgs. These permissions are removed from orgs created in Winter ’21 and later. For existing orgs, reduce object permissions for guest users if they have View All, Modify All, edit, or delete permissions on a standard or custom object.
View All Users and Other Permissions Removed in Guest User Profiles (Previously Released Update, Enforced)
Guest users typically don’t need access to view all users in a Salesforce org, so to promote data security, we disabled the View All Users permission in guest user profiles with the Summer ’20 release. The permission is removed from all guest user profiles with the Winter ’21 release. To enhance security, we also removed these permissions from the guest user profile: Enable UI Tier Architecture, Remove People from Direct Messages, View Topics, and Send Non-Commercial Email.
Improved Security for Managed Topic Images
Managed topic images that were uploaded before Winter ’21 are stored as documents and are public. Guest users can see these featured and navigational topic images even in private and unpublished communities. To improve security, new images associated with featured and navigational topics are stored as asset files and are private. Ensure that guest users in your community can see these new images.
Override Entity Permissions When Using <apex:inputField>
The new ignoreEditPermissionForRendering attribute on <apex:inputField> allows you to override entity edit permissions for users, even when the underlying permission on the object doesn’t allow edits. This override affects all users but is intended to be used only for guest users. This attribute works only with a custom controller in without sharing mode.