1. From the object management settings for the object you want to set an override for, go to Buttons, Links, and Actions.
2. Click Edit next to the button or tab home page you want to override.
3. For each experience—Salesforce Classic, Lightning Experience, or mobile—click the type of override you want associated with the action.No override (use default)—Use a customoverride provided by an installed package. If there isn't one installed, thestandard Salesforce behavior is used.Standard page—This option is available onlyfor subscribers who are overriding the actions on an installed customobject. If selected, the standard Salesforce behavior is used.Custom s-control—Use the behavior from ans-control. This option isn’t supported for mobile.Important Visualforce pages supersede s-controls. Organizations that haven’t previously used s-controls can’t create them. Existing s-controls are unaffected, and can still be edited.Lightning component—Use the behavior from aLightning component. Supported only for the Edit, New, New Event, Tab andView actions. This option isn’t supported for Salesforce Classic.Lightning page—Use the behavior from theLightning record page assigned as the org default for the object. Thisoption is available only for the View action in LightningExperience.Visualforce page—Use the behavior from aVisualforce page.Use the Salesforce Classic override—Inheritsthe behavior from the Salesforce Classic Override setting.Important Before you override a standard button with a Lightning component or Visualforce page, review implementation details in the respective developer guides.
4. No override (use default)—Use a customoverride provided by an installed package. If there isn't one installed, thestandard Salesforce behavior is used.
5. Standard page—This option is available onlyfor subscribers who are overriding the actions on an installed customobject. If selected, the standard Salesforce behavior is used.
6. Custom s-control—Use the behavior from ans-control. This option isn’t supported for mobile.Important Visualforce pages supersede s-controls. Organizations that haven’t previously used s-controls can’t create them. Existing s-controls are unaffected, and can still be edited.
7. Lightning component—Use the behavior from aLightning component. Supported only for the Edit, New, New Event, Tab andView actions. This option isn’t supported for Salesforce Classic.
8. Lightning page—Use the behavior from theLightning record page assigned as the org default for the object. Thisoption is available only for the View action in LightningExperience.
9. Visualforce page—Use the behavior from aVisualforce page.
10. Use the Salesforce Classic override—Inheritsthe behavior from the Salesforce Classic Override setting.
11. Select the name of the s-control, Lightning component, Lightning page, or Visualforce page you want to run when users click the button or tab. When overriding the New button with a Visualforce page, you canchoose to skip the record type selection page. If you do, new records youcreate aren’t forwarded to the record type selection page. Salesforceassumes that your Visualforce page is already handling record types.
12. Click Save.