Global actions versus object-specific actions
Key Takeaway
Use an object-specific action when a new record must be tied to the record the user is on. A global action can go almost anywhere, but it doesn't know which record the user is looking at.
Quick actions let users do common tasks, like creating records, logging calls, or sending email, with a few clicks. They come in two kinds: object-specific actions and global actions. The word "quick" only means that an action is one of these two kinds, not some other kind of Salesforce action.
How the two kinds differ
An object-specific action belongs to one object and works in the context of that object. It has automatic relationships to other records, which means a new record automatically links to the record the user is on.
For example, say you add an action on Account that creates contacts. A user runs it on the Acme account, and the new contact is associated with Acme.
You can put a global action anywhere actions are supported, such as:
- The Home page
- The Chatter tab
- Object pages
- Custom Lightning app pages
A global action isn't context-aware, even on an object page, so it can't fill fields with information from the page the user is on. A global create action makes a record that has no direct relationship with other records. When the new record must be tied to the current record, use an object-specific action instead.