First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Set Up Your Environments for First-Generation Managed Packages
Developer Hub
Scratch Org Allocations for Partners
Enable Dev Hub Features in Your Org
Add Salesforce DX Users
Free Limited Access License
Manage Scratch Orgs from the Dev Hub Org
Link a Namespace to a Dev Hub Org
Supported Scratch Org Editions for Partners
Environment Hub
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Free Limited Access License

Request a Salesforce Limited Access - Free license to provide accounts to non-admin users in your production org, when these users require access to only a specific app, feature, or setting. Standard Salesforce objects such as Accounts, Contacts, and Opportunities aren’t accessible with this license.

Contact your Salesforce account executive to request this license. A Salesforce admin can upgrade a Salesforce Limited Access - Free license to a standard Salesforce license at any time.

Second-Generation Managed Packages and Unlocked Packages

To create scratch orgs and unlocked or second-generation managed packages, developers require access to the Dev Hub org, which is often your production org. A Salesforce admin can then grant appropriate permissions to the Dev Hub objects (ScratchOrgInfo, ActiveScratchOrg, and NamespaceRegistry).

To give developers appropriate access to the Dev Hub org, create a permission set that contains these permissions:

  • Object Settings > Scratch Org Info > Read, Create, and Delete
  • Object Settings > Active Scratch Org > Read and Delete
  • Object Settings > Namespace Registry > Read (to use a linked namespace in a scratch org)

To provide users with the ability to create unlocked or second-generation managed packages and package versions, the permission set must also contain:

  • System Permissions > Create and Update Second-Generation Packages

If you choose to test your package in a scratch org, the Create and Update Second-Generation Packages permission is also required when creating the scratch org if you specified an ancestor version in the sfdx-project.json file. Alternatively, use the --noancestors flag with the sf org create command when you create the scratch org.

For more information, see Salesforce DX Developer Guide: Add Salesforce DX Users.

DevOps Center

DevOps Center is installed as a managed package. Most team members, such as builders and developers, don’t need to install and configure DevOps Center. You can provide these team members minimum access to the org where DevOps Center is installed by assigning them this license and the Limited Access User profile.

See Salesforce Help: Assign the DevOps Center Permission Sets

Features Not Currently Supported

  • To use Org Shape for Scratch Orgs or Scratch Org Snapshots (pilot), be sure to assign the Salesforce user license. The Salesforce Limited Access - Free license isn’t supported at this time.
  • The Salesforce Limited Access - Free license doesn’t provide access to some Salesforce CLI commands, such as sf limits api display. Contact your Salesforce admin for API limits information.