Global Action
A Global Action is a Salesforce Quick Action that lives outside any specific object and can be invoked from anywhere in the platform: the App Launcher header (plus icon), the Lightning utility bar, the mobile app, or programmatically through a Flow.
Definition
A Global Action is a Salesforce Quick Action that lives outside any specific object and can be invoked from anywhere in the platform: the App Launcher header (plus icon), the Lightning utility bar, the mobile app, or programmatically through a Flow. Global Actions let users create records, log calls, send emails, or run a Flow without first navigating to a specific record. The classic use case is the New Task or New Event entry point in the Lightning header: it sits above every page and creates a Task without requiring a related record context.
Global Actions differ from Object-Specific Actions in two ways. They are not tied to a specific sObject, so they appear in the header and mobile launchpad regardless of which record the user is on. They also do not auto-link the new record to the current page; an Object-Specific Quick Action on Account creates a Task already linked to the Account, while a Global Action creates a free-standing Task. Global Actions are the lighter-weight pattern for "start something new" workflows that are not contextually tied to an existing record.
How Global Actions enable cross-context workflows in Salesforce
Global Action types: Create, Log a Call, Send Email, Custom Visualforce, Flow, LWC
Global Actions come in several types. Create a Record creates a new record of any object (Task, Event, custom object). Log a Call creates a Task with Type set to Call and exposes call-specific fields. Send Email opens the email composer (typically for case-related or contact-related communication). Custom Visualforce launches a Visualforce page in a modal. Flow launches a screen Flow. Lightning Web Component launches an LWC in a modal. Each type covers a different workflow pattern. Create and Log a Call are the most common; Flow-backed actions are increasingly common for multi-step workflows.
Where Global Actions appear
Global Actions can be placed in three locations. The Global Publisher Layout decides which actions appear in the plus icon in the Lightning header. The Mobile App Quick Actions setting decides which appear in the Salesforce Mobile App. Lightning App Builder lets actions surface in the Utility Bar of a Lightning App. Each location has its own configuration but pulls from the same pool of Global Actions, which means a single action can appear in all three surfaces. The Global Publisher Layout is the primary surface for most desktop users.
The Global Publisher Layout
The Global Publisher Layout is a Setup-managed list of actions that appear in the plus icon on the Lightning header. Setup, Publisher Layouts, edit the default layout. Drag Global Actions in or out, reorder them. The order matters: the first action is the default keyboard shortcut target. Most orgs include New Task, New Event, New Contact, Log a Call. Custom Actions for high-frequency workflows (Submit Support Request, Quick Note, Run Weekly Report Flow) can also be added.
Building a Global Action: the Setup workflow
Setup, Global Actions, New Action. Pick the Action Type (Create a Record, Log a Call, Send Email, Flow, LWC). For Create a Record, pick the target object. Set the Label, Name, and Icon. Configure the action layout: which fields the user fills in, predefined values, field order. Save. The action becomes available to add to Global Publisher Layouts, Mobile, and App Launcher. The workflow is identical to Object-Specific Quick Actions, with the only difference being the lack of a parent sObject.
Predefined values and field automation
Global Actions support Predefined Field Values: fields that are auto-set when the action runs, often hidden from the user. A New Task action might predefine Type = Call, Status = Not Started, Priority = Normal, leaving only Subject and Due Date for the user. The predefined values are configured on the action record. The pattern reduces user effort and increases data consistency. Use it aggressively for fields the user does not need to think about.
Action layout and the field selection
Each Global Action has its own Action Layout, separate from the parent object's page layout. The Action Layout has only the fields the user fills in when running the action. For New Task, the Action Layout typically includes Subject, Due Date, Comments, Related To. Excluded fields take their values from defaults or predefined values. Action layouts are configured through the Quick Action setup in Setup, Object Manager, Global Actions, the action, Layout.
Mobile-specific behavior and the Activity Composer
On the Salesforce Mobile App, Global Actions appear in the Activity Composer (the plus icon at the bottom of the screen). The mobile version uses a touch-optimized layout and may omit fields that do not fit a phone screen. Admins can build mobile-specific actions or use the same actions in both surfaces. The mobile Global Actions are the entry point for field service techs and on-the-go sales reps creating records without opening a record first.
Building a Global Action for a cross-context workflow
Creating a Global Action is a Setup workflow: pick the type, configure the target and predefined values, build the layout, add to publishers. The whole process takes 10 to 15 minutes for a typical action.
- Open Global Actions in Setup
Setup, Quick Find Global Actions, click the link. The page lists existing Global Actions. Click New Action.
- Pick the Action Type
Pick Create a Record, Log a Call, Send Email, Custom Visualforce, Flow, or Lightning Web Component. Action Type cannot be changed after creation.
- Configure the action specifics
For Create a Record, pick the target object. For Flow, pick the Flow. For LWC, pick the component. Set Label, Name, and Icon.
- Set Predefined Field Values
On the action record, Predefined Values tab. Add field-value pairs that auto-set when the action runs. Hidden from the user; reduces input burden.
- Build the Action Layout
On the action record, Layout. Drag fields from the palette into the layout. Only fields in the layout appear when the user runs the action. Predefined values cover the rest.
- Add to the Global Publisher Layout
Setup, Publisher Layouts, edit the default. Drag the new action into the Quick Actions section. Save. The action now appears in the Lightning header plus icon.
- Add to mobile and Lightning Apps if needed
For Mobile: Setup, Mobile Apps, Salesforce Mobile App, Mobile Navigation, add the action. For Utility Bar: Lightning App Builder, edit the app, Utility Bar, add the action.
The kind of action: Create a Record, Log a Call, Send Email, Visualforce, Flow, LWC. Cannot be changed after creation.
Display label shown to users. Should describe the action in 1 to 3 words (New Task, Log a Call, Submit Support Request).
API name used in references. Defaults from the Label but must be unique within the org.
The sObject the action creates. Task, Event, Contact, custom objects are all valid.
Visual icon shown next to the label. Pick from the Salesforce Lightning Design System icon library.
- Action Type cannot be changed after creation. Clone the action to switch types.
- Global Actions do not auto-link the new record to the current page context. Use Object-Specific Actions on the page layout when context-linking is needed.
- Predefined Field Values are not validated. A predefined value that violates a Validation Rule fails silently or surfaces a confusing error to the user. Test against the full validation set.
- The Global Publisher Layout limits the number of actions shown directly; overflow goes into a More menu. Order matters; put high-frequency actions first.
- Mobile-specific actions can have different layouts from desktop. Configure both surfaces deliberately rather than expecting a single layout to fit both.
Trust & references
Straight from the source - Salesforce's reference material on Global Action.
- Global ActionsSalesforce Help
- Global Publisher LayoutsSalesforce Help
- Actions OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Global Action?
Q2. Where do global actions appear?
Q3. What can global actions do?
Discussion
Loading discussion…