---
schema_version: "1"
id: 6630b1d55631769287271c780c2a5cc9bee58c1f68e44f09baad6ce4392e6ee4
title: Standard Actions and Overrides Basics
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/components/components-using-lex-s1-action-overrides-basics.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/components-using-lex-s1-action-overrides-basics.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 717f0cb3f6dcd334ced8cb2289e050be191943c82bda12ed839fad0a5e21751e
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# Standard Actions and Overrides Basics

There are six standard actions available on most standard and all custom objects: Tab, List, View, Edit, New, and Delete. In Salesforce Classic, these are all distinct actions.

Lightning Experience and the Salesforce mobile app combine the Tab and List actions into one action, Object Home. However, Object Home is reached via the Tab action in Lightning Experience, and the List action in the Salesforce mobile app. Finally, the Salesforce mobile app has a unique Search action (reached via Tab). (Yes, it’s a bit awkward and complicated.)

## Names in Setup for Actions You an Override
This table lists the standard actions you can override for an object as the actions are named in Setup, and the resulting action that’s overridden in the three different user experiences.

|Override in Setup|Salesforce Classic|Lightning Experience|Mobile|
|-----------------|------------------|--------------------|------|
|Tab|object tab|object home|search|
|List|object list|**n/a**|object home|
|View|record view|record home|record home|
|Edit|record edit|record edit|record edit|
|New|record create|record create|record create|
|Delete|record delete|record delete|record delete|

**note:** -   “n/a” doesn’t mean you can’t *access* the standard behavior, and it doesn’t mean you can’t *override* the standard behavior. It means you can’t *access the override*. It’s the override’s functionality that’s not available.
-   There are two additional standard actions, Accept and Clone. These actions are more complex, and overriding them is an advanced project. Overriding them isn’t supported.

## How and Where You Can Use Action Overrides

Aura components can be used to override the View, New, New Event, Edit, and Tab standard actions in Lightning Experience and the Salesforce mobile app. You can use an Aura component as an override in Lightning Experience and mobile, but not Salesforce Classic.