ISVforce Guide

ISVforce Guide: Build and Distribute AppExchange Solutions
Quick Start Tutorials: Become a Partner and Build a Simple AppExchange Solution
Design and Build Your AppExchange Solution
Package and Test Your AppExchange Solution
About Managed Packages
Register a Namespace for a First-Generation Managed Package
Specifying a License Management Organization
What are Beta Versions of Managed Packages?
Create a Beta Package for First-Generation Managed Packages
Create and Upload a First-Generation Managed Package
View Package Details
Installing a Package
Uninstall a Managed Package
Install First-Generation Managed Packages Using the Metadata API
Resolving Apex Test Failures
Running Apex on Package Install/Upgrade
Running Apex on Package Uninstall
Publish Extensions to Managed Packages
Pass the AppExchange Security Review
Publish Your Solution on AppExchange
Sell on AppExchange with Checkout
Monitor Performance with Analytics for AppExchange Partners
Report Orders to Salesforce with the Channel Order App
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
Provide a Free Trial of Your AppExchange Solution
Update Your AppExchange Solution
User License Guides for Salesforce Partners
PDF

Newer Version Available

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

About Managed Packages

Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Developer Edition

Package uploads and installs are available in Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Building a new app? Have you considered using second-generation managed packages? Flexible versioning and the ability to share a namespace across packages are just two reasons why developers love creating second-generation managed packages. We think you’ll love it too. To learn more, see: Discover the Benefits of 2GP Package Development, and Comparison of First- and Second-Generation Managed Packages.

Important

A managed package is a collection of application components that are posted as a unit on AppExchange, and are associated with a namespace and a License Management Organization.

  • You must use a Developer Edition organization to create and work with a managed package.

To prevent naming conflicts, Salesforce recommends using managed packages for all packages that contain Apex to ensure that all Apex objects contain your namespace prefix. For example, if an Apex class is called MyHelloWorld and your org’s namespace is OneTruCode, the class is referenced as OneTruCode.MyHelloWorld.

Tip