If you’ve ever watched a Salesforce user stop mid-task just to navigate away and create a record — you already know the problem that global actions in Salesforce were built to solve.
Global Actions let users log calls, create records, send emails, and complete tasks without leaving the page they’re on. For Salesforce Admins, they’re one of the most impactful UI customization tools available — and a key topic on the Salesforce Administrator Certification exam.
In this complete guide, we’ll cover everything: what global actions are, the types available, how to create and configure them, how to add them to layouts, and how to deploy them across orgs. Let’s dive in.
Global actions in Salesforce are shortcuts that allow users to perform common tasks — like creating a record, logging a call, or sending an email — from almost any page in Salesforce, including the Home page, Chatter tab, and object pages.
Unlike object-specific actions (which are tied to a particular record), global actions have no automatic relationship with the record or page you’re currently viewing. They’re truly universal — available wherever the global publisher layout is active.
Key Concept: Global actions appear in the global actions menu (the “+” icon in Lightning Experience) and can be added to any page that supports actions. A global “Create a Record” action creates a new record independently — it won’t auto-populate a parent Relationship like an object-specific action would.
Global Actions vs. Object-Specific Actions
It’s important to understand the distinction:
| Feature | Global Actions | Object-Specific Actions |
|---|---|---|
| Where available | Any page in Salesforce | Only on the specific object’s record page |
| Record relationship | No automatic relationship | Can pre-populate related fields |
| Managed via | Global Publisher Layout | Object’s Page Layout |
| Typical use | Create standalone records, log calls globally | Update related records, trigger context-aware tasks |
For admin exam purposes, remember: global actions are added to the Global Publisher Layout, while object-specific actions are added to the page layout of a specific object.
6 Types of Global Actions in Salesforce
Salesforce gives you six action types to work with. Each serves a different purpose:
1. Create a Record
Creates a new record of any object (e.g., Lead, Contact, Case). The record is not automatically related to another record. This is the most commonly used global action type.
2. Update a Record
Updates fields on the current record. Note: this type is only available as an object-specific action, not a true global action.
3. Log a Call
Opens a form to log call details and create an activity record. Perfect for sales reps recording conversations on the go — right from the home page or Chatter feed.
4. Send Email
Opens a pre-configured email window. Users can send emails without navigating to a record’s activity feed. Great for quick customer communications.
5. Custom Visualforce
Launches a custom page built with Visualforce. Gives developers full control over what happens when the action is triggered. Used for complex, business-specific workflows.
6. Custom Canvas
Embeds a Canvas app inside the action panel. Used for deep integrations with third-party systems where a richer interface is needed.
How to Create Global Actions in Salesforce: Step-by-Step
Follow these steps to create a global action from Salesforce Setup:
- Go to Setup → In the Quick Find box, type Actions → Select Global Actions
- Click New Action
- Select your Action Type (Create a Record, Log a Call, Send Email, etc.)
- For “Create a Record”, choose the Target Object (e.g., Contact, Lead, Task)
- Enter a Label — this is what users will see in the action menu
- Optionally enter a Description and a custom Success Message that appears when the action is completed
- Click Change Icon to give your action a recognizable visual indicator
- Click Save
Important: Once you create an action, the Action Type cannot be changed. If you need a different type, you’ll need to create a new action. Additionally, custom images used as action icons must be smaller than 1 MB.
Configuring Action Layouts
After creating a global action, the next step is customizing its Action Layout. Think of an action layout like a mini page layout — it controls which fields appear when a user triggers the action.
When you first open a new action’s layout, Salesforce automatically pre-populates it with default fields, standard required fields, and any universally required custom fields for the target object.
How to Edit an Action Layout
- From the Global Actions list, click the action name
- Click Layout
- Drag fields from the palette onto the layout to add them
- Remove fields you don’t want users to see when taking that action
- Click Save
Best Practice: Keep action layouts lean. Only include the fields that are truly necessary for the task. If a user is logging a quick call, they don’t need 15 fields — keep it to 4 or 5 essential ones to drive adoption.
Global Publisher Layouts: Making Actions Available to Users
Creating an action is only half the work. For users to actually see and use a global action, you must add it to a Global Publisher Layout and assign that layout to the appropriate user profiles.
Key Rules for Global Publisher Layouts
- Global publisher layouts can only include global actions — not object-specific actions
- Without adding a global action to a global publisher layout, users cannot access it
- You can assign different global publisher layouts to different profiles, giving different teams access to different actions
How to Add a Global Action to the Global Publisher Layout
- Go to Setup → In Quick Find, type Publisher Layouts → Select Global Publisher Layouts
- Click Edit next to the layout you want to modify (or create a new one)
- Drag your global action from the panel into the layout
- Click Save
- To assign the layout to profiles: Go to Setup → Profiles → Select a profile → Scroll to “Global Publisher Layouts” → Edit Assignment
Exam Tip: The Salesforce Admin exam frequently tests the relationship between global actions and global publisher layouts. Remember: global actions live in the global publisher layout; object-specific actions live in the object’s page layout. Both types of actions have their own action layouts.
Ready to Master Salesforce Administration?
Global Actions are just one of the many powerful features you’ll master in the complete Salesforce Admin Certification Course at MyTutorialRack. Whether you’re a beginner or looking to upgrade your skills, this course covers everything you need to pass the Salesforce Admin exam and excel in your career.
- Hands-on Labs
- Exam-Ready Content
- Expert Instructor
How to Deploy Global Actions Between Salesforce Orgs
Once you’ve built and tested global actions in a sandbox, you’ll need to deploy them to your production org. Here’s what you need to know:
Global Actions as Metadata
In Salesforce metadata, global actions are stored as the QuickAction metadata type. This means you can deploy them using standard Salesforce Deployment tools like Change Sets, Salesforce CLI, or third-party tools like Gearset.
Deploying with Gearset (Example)
- In Gearset, set up a comparison between your source org (sandbox) and target org (production)
- Add the Quick Action metadata type to your comparison filter — or use Gearset’s Default Comparison filter, which includes Quick Action along with 60+ other metadata types automatically
- Run the comparison. New global actions appear in the “New” tab; changed actions appear in the “Changed” tab
- Select the global actions you want to deploy and click Deploy
Always include the associated Global Publisher Layout in your deployment if you’ve made changes to it — otherwise your actions won’t be visible to users in the target org.
Global Actions in the Salesforce Mobile App
Global actions work seamlessly in the Salesforce mobile app, which is a huge win for field teams. Users can log calls, create records, or send emails directly from their phones without navigating into a specific record.
The same global publisher layout controls what actions are available on mobile. Keep these mobile-specific tips in mind:
- Keep the action layout minimal — fewer fields mean faster data entry on small screens
- Choose meaningful icons so mobile users can identify actions quickly
- Test actions in both Lightning Experience and the Salesforce mobile app before rolling out to users
Real-World Use Cases for Global Actions
Here are some practical ways Salesforce teams use global actions:
Sales Teams — Log Call Action: Sales reps can log calls from anywhere in Salesforce — no need to open an opportunity record. Keeps pipeline data clean and up-to-date.
Support Teams — Create Case Action: Support agents can quickly create a new Case from the Home page or Chatter feed when a customer issue comes in.
Marketing Teams — Create Campaign Member: Marketers can add contacts to campaigns without leaving their current workflow.
Managers — Create Task Action: Managers can create tasks for team members directly from the home page or a Chatter conversation.
All Teams — Send Email Action: Any user can trigger a quick email from anywhere — great for customer acknowledgements or internal notifications.
Best Practices for Global Actions in Salesforce
- Keep action layouts focused. Only include the fields users absolutely need. Less is more.
- Use clear, action-oriented labels. “Log a Call” is better than “Call Activity” — users should instantly know what the action does.
- Assign different layouts to different profiles. Sales reps, support agents, and managers have different needs — give each profile a tailored set of actions.
- Don’t overload the action bar. Limit the number of global actions visible to any profile. If users see 15 actions, they’ll use none of them.
- Test on mobile before deploying. Always verify how actions look and function in the Salesforce mobile app.
- Document your actions. Maintain a simple log of which global actions exist, what they do, and which profiles have access.
Common Mistakes to Avoid
- Creating an action but forgetting to add it to the publisher layout — users won’t see it
- Using a “Create a Record” global action when an object-specific action was needed — the global action won’t pre-populate relationship fields
- Trying to change the action type after creation — this isn’t possible; create a new action instead
- Not testing with the correct profile — always test as a non-admin user to confirm the action appears correctly
- Deploying the action without the publisher layout — the action arrives in production but isn’t wired to any layou
Global Actions and the Salesforce Admin Certification Exam
Global actions are a consistently tested topic in the Salesforce Administrator Certification exam. Here’s what to focus on:
Exam Focus Areas
- The difference between global actions and object-specific actions
- The role of the Global Publisher Layout in making actions visible
- The available action types and their use cases
- The fact that Action Type cannot be edited after creation
- How action layouts are customized independently of page layouts
Understanding these topics deeply — not just memorizing them — will help you answer scenario-based exam questions with confidence.
Quick Reference: Global Actions in Salesforce
| Topic | Key Point |
|---|---|
| Where actions appear | Home page, Chatter tab, object pages, Salesforce mobile app |
| Record relationship | Global actions have NO automatic relationship with existing records |
| Action Type | Cannot be changed after creation |
| Publisher Layout | Global actions must be added to the Global Publisher Layout to be visible |
| Metadata Type | Deployed as QuickAction metadata |
| Action Layout | Configurable — control which fields appear in the action form |
| Profile Assignment | Different profiles can have different publisher layouts |
Conclusion
Global actions in Salesforce are one of the most user-friendly features an admin can configure. They reduce friction, speed up data entry, and help users stay focused on their workflows rather than navigating around the platform.
As a Salesforce Admin, mastering global actions means understanding not just how to create them, but how they fit into the broader ecosystem of publisher layouts, action layouts, profiles, and deployment pipelines. Get these fundamentals right and you’ll be building a Salesforce environment that users actually love to work in.
Take Your Salesforce Admin Skills to the Next Level
If this guide helped you understand global actions better, imagine what you could learn in a full, structured Salesforce Admin Certification course. From automation and security to reports and data management, there’s a lot more to explore — and a certification to earn along the way.
Ready to Master Salesforce Administration?
Global Actions are just one of the many powerful features you’ll master in the complete Salesforce Admin Certification Course at MyTutorialRack. Whether you’re a beginner or looking to upgrade your skills, this course covers everything you need to pass the Salesforce Admin exam and excel in your career.
- Hands-on Labs
- Exam-Ready Content
- Expert Instructors
