Standard Action Overrides

You can specify a different override for each user experience, with the following guidelines.

• Salesforce Classic—Use a Visualforce page as the action override.
• Lightning Experience and the Salesforce mobile app —You can override the Edit, New, Tab, and View standard actions on most standard and all custom objects.
• Lightning Experience—Use a Lightning component as the action override for the Edit, New, and Tab actions. Use a Lightning page or a Lightning component as the action override for the View action.
• Aura Experience Builder sites—Use a custom Lightning component to replace standard forms when users click the New or Edit button. The action that you choose in Lightning Experience is the same action that you use to override actions in Aura Experience Builder sites.
• Salesforce app—Use a Lightning component as the action override.
• Managed packages—Developers can include action overrides as package defaults, and managed package subscribers can specify local overrides as alternatives to the default overrides.

Note For Salesforce Classic, usually a Visualforce page is the only supported override option. Under certain conditions, you can use existing s-controls as overrides for Salesforce Classic. However, s-controls have been deprecated since the Spring ’09 release. We recommend using Visualforce pages instead.

• Assign Action Overrides
  To assign a Visualforce page or Lightning component as an override, first create the page or component (or use one created by a Salesforce developer in your org). It’s important to understand the action override options for each user experience and how your selections for each one can affect the others.
• Assign a Lightning Record Page Override for the View Action
  When you create an override for the View action for Lightning Experience, you can use either a Lightning record page or a Lightning component. To use a Lightning record page as an override, you must activate the page in the Lightning App Builder and choose the type of override you want.
• Action Overrides in Managed Packages
  In a managed package, overrides specified by the package developer are included as default overrides. The package subscriber can specify local overrides for each user experience to use instead of the package default overrides. Package default overrides impact the options and behaviors of local overrides.
• Action Overrides in Aura Experience Builder Sites
  Personalize your site users’ experience in Aura Experience Builder sites by adding a custom Lightning component to replace standard forms when users click the New or Edit button. Use action overrides when your site and portal users require a more customized user experience than the Salesforce standard page provides.