Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryMManaged Package
PlatformAdvanced

Managed Package

A Managed Package is a collection of Salesforce components (objects, classes, flows, pages, etc.) that is developed and distributed by a third-party ISV or internal team through AppExchange or dire…

§ 01

Definition

A Managed Package is a collection of Salesforce components (objects, classes, flows, pages, etc.) that is developed and distributed by a third-party ISV or internal team through AppExchange or directly. Managed Packages have their own namespace, support versioning and upgrades, and protect the developer's intellectual property by obfuscating Apex code.

§ 02

In plain English

👋 Study buddy

Here's a simple way to think about it: Managed Packages are how AppExchange products and ISV teams ship Salesforce code. Bundles of metadata distributed under a unique namespace - versionable, upgradable, protected. The standard distribution mechanism.

§ 03

Worked example

scenario · real-world use

A company installs a Managed Package called "DocuSign for Salesforce" from AppExchange. The package adds custom objects, Visualforce pages, and Apex classes that integrate e-signature functionality directly into the Opportunity record. When DocuSign releases version 8.2 with new features, the admin clicks "Upgrade" and the package updates without overwriting any local customizations.

§ 04

Why Managed Packages are how AppExchange products and ISV teams ship Salesforce code

A Managed Package is a Salesforce-shipped bundle of metadata - objects, fields, classes, flows, pages - distributed under a unique namespace, versionable, upgradable, and (importantly) protected. The Apex code inside a managed package is obfuscated; the namespace prevents collisions with the consuming org's customizations; the version history makes upgrades safe. For ISVs publishing on AppExchange and for internal teams distributing reusable packages, this is the standard distribution mechanism.

The reason it earns its own concept rather than being treated like ordinary metadata is upgrade safety. A subscriber can install version 1.0 of a managed package, then upgrade to 1.1 next quarter, and the platform handles the migration cleanly - preserving subscriber data, applying schema changes, deprecating old components. That guarantee is what makes the AppExchange model viable. Choose a managed package for anything you'll distribute beyond a single org; reserve unmanaged packages for transient or single-use bundles.

§ 05

How organizations use Managed Package

Northwind Trading

Procurement defaults to Managed Package evaluation before custom builds; saves significant development time.

BlueRiver Health

Compliance reviews verify Managed Package security posture before installation; AppExchange security review badge is starting point.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Managed Package.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

Test your knowledge

Q1. Who can benefit from understanding Managed Package?

Q2. What does Managed Package represent in the Salesforce Platform?

Q3. How does Salesforce's multi-tenant model affect Managed Package?

§

Discussion

Loading…

Loading discussion…