Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are the organization roles involved in publishing an application on the AppExchange and what is the purpose of each of these orgs?

Example org roles:

  • CRM ISV Organization (Business Org)
  • AppExchange Publishing Organization (APO)
  • Developer Edition Organizaiton
  • License Management Organization (LMO)
share|improve this question
up vote 6 down vote accepted

Update: here is a blog-post which best explains the distinctions between the various org types involved in the AppExchange publishing process:

Understanding the AppExchange publishing process, environments, and app lifecycle

As a brief summary, though, here is an explanation of the roles of each type of org:

  • Managed Package Development Org - you will need to have ONE of these for each managed package / AppExchange app that you have. Licenses for customers using each packages developed in each of these orgs can be more easily managed through the use of the LMO org. AppExchange Listings for each of these apps can be more easily managed from AppExchange by specifying your CRM/LMO org as your AppExchange Publishing Org / APO (see below). Development orgs come in 2 types/sizes:

    a. Regular Developer Edition (DE) org - has 2 System Admin users, and limited data storage. Available from

    b. Partner Developer Edition (PDE) org - a special "super-sized" development edition type appropriate for AppExchange application development. Comes with more users and higher limits.

  • LMA - the License Management Application. Each Partner should have ONE org, typically their CRM for Partners / Business org, that has this special application, available only by request from after you have become an official Partner, installed in it. Whatever org has this app installed is dubbed the "License Management Org" / LMO.

  • LMO - License Management Organization / CRM for Partners / Business org - once you have an established ISV/OEM contract with, you are given an Enterprise Edition org with 2 free licenses and one or more special applications pre-installed into it. This org, and these applications (the License Management App, and sometimes the Channel Orders App) are tools for ISV's/OEM's to use for:

    1. tracking which Packages and Package Versions you have uploaded for each of your various AppExchange packages
    2. managing customer Licenses to your AppExchange packages
    3. supporting your customers through Subscriber Grant Login Access / aka the "Partner Black Tab" functionality
    4. submitting ISV Channel Orders to to collect revenue from your sales
  • APO - AppExchange Publishing Organization - AppExchange terminology for the org that you would like to be the AppExchange listing management hub for all of your company's AppExchange apps/listings. As a best practice, make this your LMO/CRM/Business org. This will allow you to manage all of your AppExchange listings from one place. Once you have established this org as your APO, you'll be able to login to Appexchange using your APO credentials, and see and manage ALL of your AppExchange packages/listings which you have linked by clicking Manage Organizations > Link New Organization from the Publishing Console.

linking APO organizations

  • TMO - Trialforce Management Organization - where you manage your company's custom branding and create/manage your Trialforce Master Orgs. Typically this is a separate org from all of your other orgs, and is some type of Developer Edition org.
share|improve this answer
I might have got a bit mixed up interpreting the answer. I've just had a conversation with Salesforce support and they reworked my setup. "SF best practices suggests you link your LMO to your APO, this way you can add multiple DE orgs to your APO and use your APO credentials to manage both your listings (via and your leads ( ... I've switched the associations so that your APO is linked to your LMO and your DE org is a contributing org." – Daniel Ballinger Feb 27 '13 at 22:41
So, I think, the DE/PDE org that the managed package is created in shouldn't be the APO. Rather it should be linked to the APO, which is also the LMO/Business Org. – Daniel Ballinger Feb 27 '13 at 22:54
Daniel, you are correct. The APO should NOT be your DE/PDE org --- it should be your LMO/Business Org. That way if you have multiple AppExchange listings corresponding to multiple DE/PDE orgs, you can manage all listings from a single login --- your LMO/Business/"APO" login. I have updated my post, and my blog post, accordingly. – zachelrath Mar 11 '13 at 11:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.