---
schema_version: "1"
id: dd648b43f96d9c7ae13d3e6ce99db40abcca176bb354096cbdd73c12ebb6db59
title: Best Practices for the License Management App
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/lma/lma-best-practices.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/lma-best-practices.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: eaf56f113c7466181868106c62b66d14e6d1f2f0fe53ab85e3133429c04e9a8d
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Best Practices for the License Management App

Follow these best practices when you use the License Management App (LMA).

- To take advantage of entitlements that are unique to ISV partners, use your partner business org as your License Management Org.
- Create a list view filter for leads created by installed packages. The filter helps your team separate subscriber-based leads from leads coming from other sources.
- Use the API to find licensed users. The `isCurrentUserLicensed` method determines if a user has a license to a managed package. For more information, see the [Apex Reference Guide](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_methods_system_userinfo.htm).
- Treat the LMA custom objects as read-only. Use the Modify License page to edit licenses. Don’t attempt to directly or programmatically edit license records.
- The LMA automatically creates package, package version, and license records. Customizations, such as adding required custom fields or creating workflow rules, triggers, or validation rules that require custom fields, can prevent the LMA from working properly.