Global Action + Object specific action + Action Layout Editor

 

1. Global Actions

   • Actions not tied to any specific object.
   • Accessible across Salesforce (e.g., log a call, create a task, display a Visualforce Page ,  , Display a Custom Canvas ).
   • Best for universal tasks.

2. Object-Specific Actions

   • Actions tied to a specific object (e.g., create a case for an Account).
   • Context-aware and available on object record pages.
   • Best for object-related workflows.

3. Action Layout Editor

   • Tool to customize the layout of Global and Object-Specific Actions.
   • Lets you add, remove, or rearrange fields for better usability.

Key Difference: Global Actions work everywhere, while Object-Specific Actions are tied to specific objects. The Action Layout Editor customizes how fields appear in these actions.

where to define who will be able to see a Global or object action

Global Actions and Object-Specific Actions in Salesforce depends on page layouts, profiles, and permissions

---

1. For Global Actions

• Defined In:

  • Global Publisher Layouts: Determine which global actions appear in the Global Actions Menu (e.g., in the header or Salesforce Mobile App).
  • Lightning App Builder: Add Global Actions to specific Lightning pages or components (e.g., utility bar or record pages).

• Steps to Control Visibility:

  1. Go to Setup → Global Actions → Publisher Layouts.
  2. Edit the Global Publisher Layout to include or exclude specific Global Actions.
  3. Assign Publisher Layouts to specific profiles via Global Publisher Layout Assignments.

---

2. For Object-Specific Actions

• Defined In:

  • Page Layouts: Control which actions are visible on the record detail page or related lists for a specific object.
  • Compact Layouts (for Salesforce Mobile and Lightning Experience): Show specific actions in the action bar at the top of the page.

• Steps to Control Visibility:

  1. Go to Setup → Object Manager → [Object] → Page Layouts.
  2. Select the relevant page layout and add/remove the action in the "Mobile & Lightning Actions" section.
  3. Assign the layout to specific profiles using Page Layout Assignments.

---

3. Permission Considerations

• Profiles and Permission Sets:

  • Actions will only be visible to users with the required object permissions and field-level security.
  • Example: If a user lacks the "Create" permission for an object, they won’t see actions to create a record for that object.
  • Define these in Setup → Profiles or Setup → Permission Sets.

• Record Types:

  • If an action is tied to a specific record type, only users with access to that record type will see it.

---

Quick Summary

1. Use Global Publisher Layouts for global actions.
2. Use Page Layouts for object-specific actions.
3. Ensure proper permissions and field-level security for the users who need access.

This layered approach ensures actions are visible only to the right users based on their roles and responsibilities!

Om Namah Shivai !!