Salesforce DX Developer Guide

How Salesforce Developer Experience (DX) Tooling Changes the Way You Work
Provide Developers Access to Salesforce DX Tools
Select and Enable a Dev Hub Org
Enable Source Tracking in Sandboxes
Add Salesforce DX Users
Determine Which License to Assign to Dev Hub Users
Add a System Administrator or Standard User to Your Dev Hub Org
Add a Developer User to Your Dev Hub Org
Add a Limited Access User to Your Dev Hub Org
Create and Assign a Permission Set to Developer Users
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Work with Data
Salesforce DX MCP Server and Tools
Development
Build and Release Your App
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Create and Assign a Permission Set to Developer Users

To give full access to the Dev Hub org, create and assign a custom permission set that grants access to required Dev Hub objects. Or if you have the Developer license, assign the Developer permission set.

Standard Developer Permission Set

If you're providing access to the Dev Hub org using the standard Developer license, it also includes a built-in Developer permission set. This permission set provides the required permissions for scratch orgs, and unlocked and second-generation managed packaging. You can use the provided Developer permission set or create your own.

Create a Permission Set

Follow the steps to create a permission set, then add the required scratch org and packaging permissions.

Required Permissions for Scratch Orgs

  • Object Settings > Scratch Org Infos > Read, Create, Edit, and Delete
  • Object Settings > Active Scratch Orgs > Read, Edit, and Delete

Required Permissions for Unlocked Packaging and Second-Generation Managed Packaging

To work with unlocked or second-generation managed packages in the Dev Hub org, the permission set must contain the scratch org permissions and:

  • Object Settings > Namespace Registries > Read
  • System Permissions > Create and Update Second-Generation Packages

The system permission provides access to:

Salesforce CLI Command Tooling API Object (Create and Edit)
package create Package2
package version create Package2VersionCreateRequest
package version update Package2Version

Assign Permission Set to Users

To assign one or more users to a permission set, or to remove a user from a permission set, see Manage Permission Set Assignments in Salesforce Help.