Loading

Apex:outputField and certain Lightning components are no longer supported when Edit permission is disabled

Data pubblicazione: Jun 25, 2026
Descrizione

Timeline for Guest User Object Permission Changes
Guest User Object Permission Changes are slated to be turned off for custom objects and certain standard objects with the rollout of the Winter '21 release. You can activate the "Opt Out of Enforcing Guest User Object Permission Changes" critical update to keep these permissions unchanged until Spring '21. After your org updates with the Winter '21 release, this update can no longer be activated, and these permissions are permanently removed in the Spring '21 release.

Impacts on Apex:outputField and Lightning Components
Apex:outputField: The apex:outputField component with inline edit is not supported if Edit permission on the object is not enabled for the Guest User profile. Since the inline edit feature makes the field editable, Guest Users require Edit permission for the component to work properly. When Edit permission is removed, the apex:outputField renders in read-only mode only.

Example: When a user double-clicks on a field rendered by apex:outputField with apex:inlineEditSupport, the field becomes editable if the user has Edit permission. Without Edit permission, the field remains in read-only mode regardless of double-clicking.


<apex:outputField value="{!SalesforceObject.FirstName}">
  <apex:inlineEditSupport event="ondblClick"/>
</apex:outputField>


Lightning components that require Edit permission:
The following Lightning components require object Edit permission and Read/Write record access to render in edit mode. When Edit permission is removed for Guest Users:

  • lightning:recordEditForm and lightning:inputField — shows an error message
  • force:recordEdit — shows an error message
  • lightning:recordForm — renders in Read Only mode when only Read permission is granted; edit is not available
  • File Upload screen component in Flows — stops working for Guest Users


 

Risoluzione

Workarounds
Activate the "Opt Out of Enforcing Guest User Object Permission Changes" critical update to retain Edit and other permissions until the Spring '21 release.
For longer-term solutions, record modification needs for Guest Users should be addressed by executing updates in Apex methods that run in "without sharing" mode, combined with encryption and decryption of resources. Alternative UI components such as lightning:input and force:inputField can be used instead of the components that require Edit permission.

Running Flows in System Context
As an alternative, run Flows in system context. This mode allows the standard Flow actions "Get Records" and "Update Records" to work for Guest Users without requiring Apex actions or Edit permissions.

Risorse aggiuntive
Numero articolo Knowledge

000393226

 
Caricamento
Salesforce Help | Article