ActionsSettings Metadata Type in SFDX

Architectural Overview#

The ActionsSettings metadata type manages org-wide settings for the Salesforce Action framework, including Chatter Publisher actions, default Quick Actions (LogACall, NewTask, NewEvent, SendEmail), and third-party Action Links.

In Lightning Experience and the Salesforce Mobile App, the highlight panel and activity composer rely on the interaction between ActionsSettings, Global Publisher Layouts, and object-specific Layout <platformActionList> blocks. Tracking ActionsSettings in version control ensures consistent action rendering across scratch orgs, sandboxes, and production.

Directory and File Conventions#

In SFDX source format (apiVersion 68.0), ActionsSettings lives in the settings/ directory and is retrieved via Settings:Actions.

Key Metadata Fields#

The ActionsSettings XML schema exposes the following boolean flags:

Declarative XML and Package Manifest Examples#

Below is the standard Actions.settings-meta.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<ActionsSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableDefaultQuickActions>true</enableDefaultQuickActions>
    <enableThirdPartyActions>true</enableThirdPartyActions>
</ActionsSettings>

Scratch Org Configuration (config/project-scratch-def.json)#

{
  "orgName": "Lightning Actions Scratch Org",
  "edition": "Enterprise",
  "settings": {
    "actionsSettings": {
      "enableDefaultQuickActions": true,
      "enableThirdPartyActions": true
    }
  }
}

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Actions</members>
        <name>Settings</name>
    </types>
    <version>68.0</version>
</Package>

CLI Retrieval and Deployment Commands#

Retrieve and deploy ActionsSettings using Salesforce CLI:

# Retrieve Actions.settings-meta.xml from the org
sf project retrieve start --metadata Settings:Actions

# Deploy Actions.settings-meta.xml to the target org
sf project deploy start --metadata Settings:Actions

Architect Best Practices and Gotchas#

• Migrate to Dynamic Actions on FlexiPage: While ActionsSettings and Layout <platformActionList> govern legacy layout-driven buttons, modern Lightning architecture uses Dynamic Actions directly inside FlexiPage metadata so visibility rules can be evaluated per record field and permission without multiplying page layouts.
• Email Deliverability Dependency: The standard SendEmail quick action will remain hidden from users even when enableDefaultQuickActions is true if the target sandbox has Email Deliverability set to No Access or System Email Only.

Frequently asked questions

What does the ActionsSettings metadata type control in Salesforce?

ActionsSettings controls org-level flags for Quick Actions, including enabling default quick actions on page layouts and enabling third-party action links in Chatter feeds.

How is ActionsSettings referenced in a package.xml manifest?

Use the Settings metadata type with the member name Actions inside your package.xml file.

Where is the ActionsSettings file stored in an SFDX repository?

It is stored at force-app/main/default/settings/Actions.settings-meta.xml.

Why are standard Log a Call or New Task actions missing on a layout?

If enableDefaultQuickActions is disabled in ActionsSettings or the layout overrides the global publisher layout without including mobile and Lightning actions, those buttons will not render.