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

# Best Practices for Feature Management

Here are some best practices when working with feature parameters.

- We recommend that you use this feature set in a test package and a test LMO before using it with your production package. Apply changes to your production package only after fully understanding the product’s behavior.
- Create LMO-to-subscriber feature parameters to enable features from your LMO for individual subscriber orgs. Don’t use the Apex code in your managed package to modify LMO-to-subscriber feature parameters’ values in subscriber orgs. You can’t send the modified values back to your LMO, and your records will be out of sync.

  Use LMO-to-subscriber feature parameters as read-only fields to manage app behavior. For example, use LMO-to-subscriber feature parameters to track the maximum number of permitted e-signatures or to make enhanced reporting available.

- Create subscriber-to-LMO feature parameters to manage activation metrics. Set these feature parameters’ values in subscriber orgs using the Apex code in your managed package. For example, use subscriber-to-LMO feature parameters to track the number of e-signatures consumed or to check whether a customer has activated enhanced reporting.