AppExchange Publishing Organization
An AppExchange Publishing Organization is a Salesforce org designated by an ISV (Independent Software Vendor) as the source org from which managed packages are uploaded and published to the AppExchange.
Definition
An AppExchange Publishing Organization is a Salesforce org designated by an ISV (Independent Software Vendor) as the source org from which managed packages are uploaded and published to the AppExchange. It is where the package's namespace is registered and where new versions of the managed package are developed, tested, and released.
In plain English
“An AppExchange Publishing Organization is the special Salesforce org a partner uses to build and release their AppExchange app. Think of it like a publisher's workshop: it's where new versions are created, tested, and sent out to customers.”
Worked example
Larkfield Software, an ISV, registers an AppExchange Publishing Organization for their managed package - a Developer Edition org dedicated to building, testing, and publishing the package. The publishing org owns the package's namespace prefix (larkfield), holds the package definition, and is the source from which every new version uploads to AppExchange. Engineering develops in branched scratch orgs and merges into the publishing org for release; releases tagged in the publishing org become the AppExchange listing's available versions. The publishing org isn't where customers run the package - it's where the package itself is built.
Why AppExchange Publishing Organization matters
The AppExchange Publishing Organization (often called the 'packaging org') is the Salesforce org that an ISV designates as the source of a managed package. This org holds the package's registered namespace (a unique prefix like acme__ that appears on all the package's metadata), and it is the only place from which new versions of the managed package can be uploaded to Salesforce for distribution.
Because a managed package namespace is tied permanently to a single publishing org, ISVs treat this org with care. Losing access to it or corrupting its metadata can block all future releases of the package. Modern Salesforce development practices encourage ISVs to use Developer Hub-linked scratch orgs for actual development work and to use the publishing org primarily as a packaging step in the CI/CD pipeline, which protects the packaging org from day-to-day changes and mistakes.
How organizations use AppExchange Publishing Organization
Set up a dedicated AppExchange Publishing Organization for their ISV product and enforced a rule that no one does development directly in it. All development happens in scratch orgs, and the packaging org is used only for final package version creation.
Lost hours of investigation time when a junior developer made a metadata change directly in their publishing org that conflicted with the next release. After that incident, they locked down profile access to the packaging org to senior release engineers only.
Advises ISV clients to treat the AppExchange Publishing Organization as a production asset with backup, access control, and change management policies equivalent to what they'd use for a production Salesforce org.
Trust & references
Straight from the source - Salesforce's reference material on AppExchange Publishing Organization.
- About Managed PackagesSalesforce Developers
Test your knowledge
Q1. What is the AppExchange Publishing Organization?
Q2. Why should the publishing org be treated carefully?
Q3. What is the recommended development practice for ISVs using a publishing org?
Discussion
Loading discussion…