The document discusses the License Management Application (LMA) which allows ISV partners to manage licenses for their applications installed in customer orgs via the AppExchange. The LMA creates lead and license records for installed packages, giving partners insights into users and usage. It should be installed in the partner's business org. Key aspects covered include prerequisites to use the LMA, associating packages, and using the LMA tabs for leads, licenses, packages, versions, and subscriber support. Best practices are outlined around installation, access roles, and keeping license settings and versions consistent.

1. License Management
Application (LMA) Slides

2. What This Deck Will Cover
• What is the License ManagementApplication
• How to get the License ManagementApplication
• Installing the License ManagementApplication
• Partner Business Org (License Management Org)
• Associating Your Managed Package to YourAppExchange Publishing Console
• Inside the License ManagementApplication

3. What is the License Management Application?
• An application to manage your licenses
• Applies licensing to your uploaded and
registeredAppExchange apps
• Creates lead and license records for each
installation of your package

4. Why is the LMA important?
• Gives you full control over your application after it is installed into your customer’s or
prospect’s Org
• Records basic information about your customers or prospects after they install your
application
• Integral part of your sales, billing and marketing process
• Gives you the ability to support your customers through the Subscriber Console

5. Pre-requisites to use the LMA
• Join the Salesforce Partner Program for ISV Partners and be a revenue sharing
partner
– Go to http://p.force.com/isvprogram to learn about the requirements of the Program
– To join the Partner Program for ISVs, sign up at partners.salesforce.com
• Use a Managed Package
• App must have passed the security review

6. How do I get the LMA?
• The LMAmay already be installed in your
Partner Business Org
• If not, submit this case in the Partner
Community
– Click Support Tab
– Select the New Case Button
– Select LMA(under ISV Technology)

7. How do I get the LMA (continued)?
• Track Case
– Track the Status associated to each Case
Number
• Once Case is resolved you will be
provided a link to the LMA
– Next Step! – Install the LMA(details on next
slide)

8. Installing the LMA
• Installation should happen in the Org where you run your business and is anActive Org
(this is your Partner Business Org)
– If you do not have a Partner Business Org, we provide you two free CRM (Enterprise Edition) licenses that
become your Partner Business Org
– If you have an active salesforce.com Org we provide you two free Enterprise Edition Licenses to help run
your ISV business. Your active salesforce.com then becomes your Partner Business Org
• Follow the steps in the ISVforceGuide for installation of the LMA

9. Partner Business Org (LMO)
• Partner Business Org (LMO)
– The Partner Business Org is sometimes referred to as License Management Org (LMO) in the ISVforce
Guide
– The Partner Business Org is used to track where your package is installed or uninstalled
– LMAis the app that is installed into the Partner Business Org (LMO)
– LMAmay be pre-installed; to check, go to your Partner Business Org and look for “License Management
Application” in the top right drop-down menu
– Once LMAis installed it’s irreversible, so make sure you are installing into the correct Org

10. Installation Best Practices
• Rule of Thumb: LMAshould always be installed into the Org you run your business. This
should be the Org your Sales Representatives log into to access their leads, accounts,
contacts, and opportunities
• Important! Once you install the LMA, you cannot uninstall it
• Reminder! LMAonly works with managed packages, not unmanaged or beta packages

11. Associating Your Managed Package to Your AppExchange
Publishing Console
• Why is this important?
– To get your installations from theAppExchange into your
Partner Business Org (LMO). You will not get license
records until you have associated your package
• How do I complete this step?
– Go into theAppExchange Publishing Console
– Have your salesforce.com credentials ready
– Credentials to your Partner Business Org (LMO)
– Follow these instructions
Tip: All subsequent versions of your application will be associated to the Partner Business Org
(LMO), therefore you only need to link it once

12. Inside the LMA
• Five tabs display data specific to the
LMA:
– Leads
– Licenses
– Packages
– Package Versions
• (specific version installed)
– Subscribers (Support)

13. Leads
• When a customer or prospect installs a
managed package, a lead is automatically
created in the LMO
• The lead contains the installer's name,
company, and email address
• This information is important because it
links the license to an actual Salesforce
user
• The lead source defaults to Package
Installation

14. Lead Record
Basic Lead Data

15. License
• When LMA linked app is installed,
Salesforce creates a license record in the
LMA
• There is a single unique identifier of who
has installed the package specific to Org
ID
• You can click a license name to view
details including status, package version,
owner, and install date
• Modify any of the license settings to make
changes in the subscriber Org

16. License Record
Important
dates about
your end
customer’s
trial
Org ID for your
prospects or
customers

17. Packages
• Package records in the LMArefer to apps
that have been linked to the Partner
Business Org (LMO)
• From the Packages tab, click a package
name to view package details and license
records for install history

18. Packages Record
Unique identifier for
this managed package
Latest version of
your managed
package

19. Package Versions
• Package versions represent specific
versions of your app
• Apackage version typically contains new
functionality or enhancements from the
previous release
Best Practice - ensure all subscribers are
on the same version of your package

20. Package Version Record
Unique
identifier for
this Package
Version
Version of your managed
package
Licenses associated to your Managed
Package

21. Subscribers
• Dynamic information about Orgs that
have installed your package
• Real-time information aboutAPI and Data
Consumption
• Ability for subscribers to grant login
access to help you troubleshoot support
issues

22. Subscribers Record (Subscriber Console)
Where you would be able to gain access to your customers or prospects org
Where you can see how much file and data
storage is being sued in your prospect or
customers org API consumption of your
customer or prospect's
org
Edition of the Org
your end
customer or
prospect is on

23. Best Practices for the LMA
• Do your homework before installing and configuring
• Test ensure everything is working properly
• Make sure the appropriate people in your company have access (roles)
• Always ensure license settings match submitted orders to Salesforce
• Reference Your ISVforce Guide for specific steps

24. Next Steps
1. Follow the “Onboarding Checklist”
2. Review all resources in the Partner Community – Distribute page
– Watch the License ManagementApplication (LMA) Demo
– Check out the ISVforce Guide for more information