You are here:
How Predefined Actions Are Ordered in the Salesforce Mobile App Action Bar and List Item Actions
Your org’s page layouts and publisher layouts control the order in which actions appear in the Salesforce mobile app action bar and list item actions. If you don’t customize the actions in the action bar on a page layout or global publisher layout, Salesforce predefines the location of key actions.
Predefined actions are derived from the Quick Actions in the Salesforce Classic Publisher section of the object page layout or global publisher layout.
| Layout | Behavior |
|---|---|
| On object page layouts, when the Salesforce mobile app section isn’t customized. | If you customized the Quick Actions in the Salesforce Classic Publisher section, the quick actions in the action bar reflect those customizations. If you didn’t customize either section, the quick actions in the action bar come from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| On global publisher layouts, when the Salesforce mobile app section isn’t customized. | If you customized the Quick Actions in the Salesforce Classic Publisher section, the quick actions in the action bar reflect those customizations. If you didn’t customize either section, the quick actions in the action bar for global pages default to a Salesforce predefined set. |
Here’s the breakdown of which actions are contained in each group for each object or page. Keep in mind these considerations.
- The predefined actions in the action bar, list item actions, and associated action menus are divided into groups. The arrangement of these groups is fixed.
- Unless they’re in an ordered list, the order of actions within the groups can vary based on the object and the actions present on the global publisher layout or on an object’s page layout.
- Some actions are in fixed positions. Actions in a numbered list appear in this fixed
position in the action bar, list item actions, and in the respective action menus.
- For example, for the Account object, the standard Chatter Post action is in the fourth position. This position is fixed. Regardless of where you put the Post action in the account page layout, Post always displays in the fourth position.
- However, deletion of actions is respected. So in our example, if you delete the Post action from the account page layout, the remaining actions move up and you see Edit in the fourth position.
- Some action groups aren’t supported for every object or page.
| Action Group | Predefined Actions |
|---|---|
| 1 | Actions from the Quick Actions in the Salesforce Classic Publisher section of the Case page layout. If that section isn’t customized, quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout |
| 2 | Edit |
| 3 | Action group 3 isn’t supported for the Case object. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the page layout.* |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the page layout. |
| 6 | Productivity actions aren’t supported for this object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Call, 2. Send Email, 3. New Task, 4. New Event |
| 2 | Edit |
| 3 | Remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Contact page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the page layout.* |
| 5 | Remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the page layout. |
| 6 | Send Text |
| Action Group | Predefined Actions |
|---|---|
| 1 | The first four actions in the order defined on the page layout. If the Quick Actions in the Salesforce Classic Publisher section of the page layout isn’t customized, then the first four actions in the order defined on the global publisher layout. |
| 2 | Edit |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the page layout. If that section isn’t customized, remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the page layout.* |
| 5 | Remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the page layout. |
| 6 | Action group 6 isn’t supported for custom objects. |
| Action Group | Predefined Actions |
|---|---|
| 1 | Quick actions in the order defined on the layout. Standard Chatter actions aren’t supported. |
| 2 | Edit, Delete |
| 3–6 | Action groups 3–6 aren’t supported for the Event object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | Quick actions in the order defined on the global publisher layout |
| 2–6 | Action groups 2–6 aren’t supported for the Feed object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | Actions from the Quick Actions in the Salesforce Classic Publisher section of the Group page layout. If that section isn’t customized, quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 2–4 | Action groups 2–4 aren’t supported for the Group object. |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the page layout. |
| 6 | Action group 6 isn’t supported for the Group object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Log a Call, 2. New Task, 3. Convert (if enabled), 4. Post |
| 2 | Edit |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Lead page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the Lead page layout.* |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the Lead page layout. |
| 6 | In order: Call, Send Text, Send Email |
| Action Group | Predefined Actions |
|---|---|
| 1 | Global actions in the order defined in the Lightning page. |
| 2–6 | Action groups 2–6 aren’t supported for “App Page” Lightning pages. |
| Action Group | Predefined Actions |
|---|---|
| 1 | New |
| 2–6 | Action groups 2–6 aren’t supported for list views. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. New, 2. Sort |
| 2–6 | Action groups 2–6 aren’t supported for object home pages. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Log a Call, 2. New Task, 3. New Event, 4. Post |
| 2 | Edit |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Opportunity page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the Opportunity page layout.* |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the Opportunity page layout. |
| 6 | Action group 6 isn’t supported for the Opportunity object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Call, 2. Send Email, 3. Post |
| 2 | Action group 2 isn’t supported for the Person object. |
| 3 | The remaining actions in the order defined on the global publisher layout |
| 4–6 | Action groups 4–6 aren’t supported for the Person object. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Call, 2. Send Email, 3. New Task, 4. New Event |
| 2 | Edit |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Person Account page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the Person Account page layout.* |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the page layout. |
| 6 | Read News, Send Text, View Website |
| Action Group | Predefined Actions |
|---|---|
| 1 | New |
| 2–6 | Action groups 2–6 aren’t supported for related lists. |
| Action Group | Predefined Actions |
|---|---|
| 1 | Quick actions in the order defined on the global publisher layout |
| 2–6 | Action groups 2–6 aren’t supported for the Salesforce Today main page. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Quick Message, 2. Join Conference Call, 3. Map |
| 2 | Action group 2 isn’t supported for Salesforce Today mobile calendar events. |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Event page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. |
| 4–6 | Action groups 4–6 aren’t supported for Salesforce Today mobile calendar events. |
| Action Group | Predefined Actions |
|---|---|
| 1 | 1. Edit Comments, 2. Change Date, 3. Change Status, 4. Change Priority |
| 2 | Edit |
| 3 | The remaining quick actions from the Quick Actions in the Salesforce Classic Publisher section of the Task page layout. If that section isn’t customized, the remaining quick actions are inherited from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. Standard Chatter actions aren’t supported. |
| 4 | Custom buttons that are supported in the Salesforce mobile app, in the order defined on the Task page layout.* |
| 5 | The remaining standard buttons that are supported in the Salesforce mobile app, in the order defined on the Task page layout. |
| 6 | Action group 6 isn’t supported for the Task object. |
* Custom buttons that are added to the Button section of a page layout and that define the content source as URL or Visualforce are supported in the Salesforce mobile app. Remember that Visualforce pages must be enabled for use in the Salesforce mobile app. Custom links, custom buttons that are added to list views, and custom buttons that define the content source as OnClick JavaScript aren’t available in the Salesforce mobile app.

