--- schema_version: "1" id: 2bce4ecf1a64113f79c9eb759dfcffd7fa740cafaaa883833c4abbfad8cb3588 title: Quick Action Considerations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/actions_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.actions_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 684f6116832e8080613371b58f0fb4345829796b782a9f6ae9c0faabf499d181 description: Keep these considerations in mind when working with quick actions. products: - Salesforce Platform - Security release: "264" --- # Quick Action Considerations Keep these considerations in mind when working with quick actions. ### Required Editions ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_important.png) Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
Actions available in: both Salesforce Classic and Lightning Experience
Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, Database.com, and Developer Editions
- 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 Printable View action is supported on Lightning Experience for desktop only. It isn’t supported on mobile devices. - To see an object-specific action on a page layout, a user must have both Read and Edit permissions on the action’s relationship field. The relationship field is the field that’s automatically populated on the target object when a user creates a record using an action. For example, for an action on a case that lets users create child cases, the default relationship field is Parent Case. To be sure that users can see the Create Child Case action, check that they have both Read and Edit permissions on the Parent Case field. Field-level security sets the Account parent field on the Case object to read-only by default, which means it’s not visible to non-system administrator users. Therefore, actions on accounts that have Case as the target object are also not visible to users without the System Administrator profile. To let users see actions on accounts that have Case as the target object, remove the Read Only setting. - In quick action layouts: - A blank space inserted on the same line as another field in the quick action layout causes that field to stretch to the full page width. The field is left justified on the page, regardless of its position in the quick action layout editor. If you add a field only to the right column in a two-column layout, the field label stretches to the full width - Two blank spaces inserted on the same row in the quick action layout editor don't create a blank line on the page. There's extra spacing between the rows as a result of the black spaces. - If there's an uneven number of fields on the quick action layout, the final field stretches to the full page width and is left justified. The behavior is the same if a blank space is inserted on the same row as the final field. - Custom actions can be defined for person accounts but with these exceptions. - Person account-specific fields, including Email and Mobile, aren’t available in action layouts when using object-specific custom actions to update accounts. - To set up object-specific custom quick actions that create person account records, define a custom lookup field for Account on the Account or Contact object. Global custom quick actions can be used without defining this field. - Actions that create business account records from a person account detail page must be global, not object-specific. - If you delete an action, the action is removed from all layouts that it’s assigned to. - Automatic triggers that change record ownership can affect what object details are visible to users. In some cases, a user can enter information that is then immediately hidden from them if an automatic trigger changes the object's owner. For example, if you use a global create quick action to create an object and an automatic trigger changes the object ownership, some information about the object isn't visible to you. - Chatter groups without customers display the global publisher layout by default, unless you override it with a customized group publisher layout. In Chatter groups that allow customers, the publisher displays standard actions only, such as Post, File, Link, and Poll. - When you create a custom quick action, use a unique label and API name. If the custom quick action has the same API name as a legacy standard action, Metadata API and change set deployment errors can occur. The incorrect action can also appear on page layouts. ## Actions and Master-Detail Object Relationships - Actions to create records for an object that is the detail object in a master-detail relationship must be object-specific, not global. - If you create an action on a detail object in a master-detail relationship, the action’s target object can’t be a different detail object of the same master. For example, master object A has two detail objects, B and C. You can create actions on object A with B or C as the target object. However, when creating an action on object B, the target object can’t be object C because B and C have the same master. To create an action on B with C as the target, you can do one of the following: - Change the relationship between B and C to master-detail so that A is the master of B, and B is the master of C. - Change the relationship between C and A to a lookup relationship. A is still the master of B with this option, so you can’t create a quick action on B with a target object of A.