Subscriber Organization
In Salesforce managed packaging, the customer's Salesforce org where a managed package has been installed, which receives push upgrades and patches from the package developer's org.
Definition
In Salesforce managed packaging, the customer's Salesforce org where a managed package has been installed, which receives push upgrades and patches from the package developer's org.
In plain English
“A Subscriber Organization is the customer's Salesforce org where a managed package has been installed. It receives push upgrades and patches from the package developer's org. It's the technical term for where the installed package lives.”
Worked example
When a customer of Pinemoor Software's ISV partner installs the partner's managed package, the customer's Salesforce org becomes a Subscriber Organization. The partner's License Management Application (LMA) records the new Subscriber Organization with its org ID, edition, user count, and version of the package installed. When the partner publishes a Patch Release v2.4.1, the Subscriber Organization receives the upgrade automatically (or via push from the LMO depending on configuration). "Subscriber Organization" is the technical term ISVs use for any customer org running their package.
Why Subscriber Organization matters
In Salesforce managed packaging, the Subscriber Organization is the customer's Salesforce org where a managed package has been installed, which receives push upgrades and patches from the package developer's org. The subscriber org is distinct from the developer org where the package was created.
Understanding the relationship between developer orgs and subscriber orgs is important for ISV work. Package code runs in the subscriber org's context, subject to the subscriber's security model and governor limits. Push upgrades and patches flow from developer org to subscriber org. Mature ISV practices test packages in environments that simulate subscriber org conditions.
How organizations use Subscriber Organization
Tests packages in environments simulating subscriber org conditions before pushing upgrades.
Tracks subscriber orgs and their installed package versions.
Understands the developer-subscriber org relationship for ISV development.
Trust & references
Straight from the source - Salesforce's reference material on Subscriber Organization.
- Second-Generation Managed PackagesSalesforce Developers
Test your knowledge
Q1. What is a Subscriber Organization?
Q2. Where do upgrades come from?
Q3. What context does the package run in?
Discussion
Loading discussion…