First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
Feature Parameter Metadata Types and Custom Objects
Set Up Feature Parameters
Use LMO-to-Subscriber Feature Parameters to Enable and Disable Features
Track Preferences and Activation Metrics with Subscriber-to-LMO Feature Parameters
Hide Custom Objects and Custom Permissions in Your Subscribers’ Orgs
Best Practices for Feature Management
Considerations for Feature Management
AgentExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Hide Custom Objects and Custom Permissions in Your Subscribers’ Orgs

Occasionally, you want to include custom permissions or custom objects in a package but not show them to your subscribers. For example, if you're piloting a feature for a few select orgs, and want to hide custom permissions and custom objects related to the pilot feature.

Check with your company’s legal team before releasing hidden functionality.

Note

To hide custom objects when creating your package, set the value of their Visibility field to Protected. After you've set the visibility to Protected, you can later update it to Unprotected. To change the visibility of an object, use the CustomObject Metadata API and update the visibility field.

To hide custom permissions when creating your package, from Setup, enter Custom Permissions in the Quick Find box. Select Custom Permissions | Your Custom Permission | Edit. Enable Protected Component, and then click Save. After your package is installed, use the System.FeatureManagement.changeProtection() Apex method to hide and unhide custom objects and permissions.

After you’ve released unprotected objects to subscribers, you can’t change the visibility to Protected.

Warning

To hide custom permissions in released packages:
  • System.FeatureManagement.changeProtection('YourCustomPermissionName', 'CustomPermission', 'Protected');
To unhide custom permissions and custom objects in released packages:
  • System.FeatureManagement.changeProtection('YourCustomPermissionName', 'CustomPermission', 'Unprotected');
  • System.FeatureManagement.changeProtection('YourCustomObjectName__c', 'CustomObject', 'Unprotected');