--- schema_version: "1" id: e131606e407e49d051e0585c7f58fa3c5b7f48944fbce7d85397ce1d41de512e title: Considerations for Actions in the Salesforce Mobile App collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/actionbar_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.actionbar_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a618353388437309937d2e29847c608f9d4f86877a64807cc036465ef7315a1f description: Keep these considerations in mind when you configure actions for use in the Salesforce mobile app. products: - Salesforce Platform - Security release: "264" --- # Considerations for Actions in the Salesforce Mobile App Keep these considerations in mind when you configure actions for use in the Salesforce mobile app. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, Database.com, and Developer Editions
- Most actions, including quick actions, productivity actions, and standard and custom buttons, are displayed in the action bar in the Salesforce mobile app. - The Save & New action button isn’t available in the Salesforce mobile app. - The Delete action is available on record pages only, not record detail pages. - In most cases, a productivity action appears only if a record includes the information that the action is keyed to. For example, the Send Email action depends on the record including an email address. The View Website action requires the record to include a website URL. On accounts, the Call action appears even when there isn’t a phone number on the record. - By default, the Call productivity action in the mobile app action bar uses the global Log A Call action layout. If you create one Log a Call action on an object, users see that custom Log a Call action’s layout when they tap **Call** from the object's action bar. If you create more than one Log a Call action for the same object, the Call action on that object uses the global Log a Call action layout. - There are a few differences between the Send Email quick action in Salesforce and the standard Email action in Case Feed: - Users can’t switch between the rich text editor and the plain text editor in a Send Email action. - Templates aren’t supported in the Send Email action. - Quick Text isn’t available in the Send Email action. - The Send Email action doesn’t support attachments. - Users can’t save messages as drafts when using the Send Email action. - Users can’t edit or view the From field in the Send Email action. - If feed tracking isn’t enabled on an object, only nonstandard actions appear in the Salesforce mobile app action bar and in third-party apps that use action lists. Nonstandard actions include Create, Update, Log a Call, custom actions, and Mobile Smart Actions. - If you’re using record types in your org, sometimes quick actions aren't visible to your users. For more information, see [Quick Actions and Record Types](https://help.salesforce.com/s/articleView?id=platform.actions_and_record_types.htm&release=264.0.0&type=5 "Using record types in your organization can affect the availability of quick actions for your users."). - The Mobile Smart Actions element appears as a single action element in the page layout editor, but it expands to several actions when it appears in the Salesforce mobile app. If the Mobile Smart Actions element is in Quick Actions in the Salesforce Classic Publisher section when you customize the action bar section, the actions in the app use your action bar customizations. In this case, the Mobile Smart Actions element in the Quick Actions in the Salesforce Classic Publisher section becomes irrelevant. - To customize the actions in the Salesforce mobile app action bar for standard and custom objects, first override the predefined actions. You can then add or remove actions from the Salesforce Mobile and Lightning Experience Actions section. For instance, to move the Join Group, Edit Group, or Leave Group actions on groups in the Salesforce mobile app, override the predefined actions in the Groups page layout. - Using URL custom buttons to pass parameters to standard pages in Salesforce Classic, such as prepopulating fields when creating a record, doesn’t work in the Salesforce mobile app. - If you add a custom button to the Salesforce Mobile and Lightning Experience Actions section of a page layout, it has a lightning bolt icon in the Salesforce mobile app action bar. If the Salesforce Mobile and Lightning Experience Actions section isn't customized, the icon in the app action bar is a wrench. #### See Also - [How Actions Are Ordered in the Salesforce Mobile App Action Bar](https://help.salesforce.com/s/articleView?id=platform.actionbar_how_actions_are_ordered_customization.htm&release=264.0.0&type=5 "The Salesforce Mobile and Lightning Experience Actions section of a page layout and global publisher layout drives which actions appear in the Salesforce mobile app action bar. You can also customize the order of quick actions, productivity actions, and standard and custom buttons that are available as actions.") - [How Predefined Actions Are Ordered in the Salesforce Mobile App Action Bar and List Item Actions](https://help.salesforce.com/s/articleView?id=platform.actionbar_how_actions_are_ordered.htm&release=264.0.0&type=5 "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.") - [Create Dynamic Actions in Lightning App Builder](https://help.salesforce.com/s/articleView?id=platform.lightning_app_builder_create_dynamic_action.htm&language=en_US)