ISVforce Guide

ISVforce Guide: Build and Distribute AppExchange Solutions
Get Ready to Distribute on AppExchange
Use Managed Packages to Develop Your AppExchange Solution
Manage Orgs with Environment Hub
Architectural Considerations for Group and Professional Editions
Security Requirements for AppExchange Partners and Solutions
Pass the AppExchange Security Review
Manage Your AppExchange Listings
AgentExchange Go-To-Market App Guide
Prerequisites and Considerations
Building Blocks of the Go-To-Market App
Go-To-Market App Transaction Lifecycle
Get Started with the AgentExchange Go-To-Market App
Undertand Invoices and Payouts
Understand Licensing in the Go-To-Market App
Use Permission Set Licenses to Sell Tier-Based Products
Your Customers and the Go-To-Market App
Migrate Existing Orders to the Go-To-Market App
Sell on AppExchange with Checkout
Report Orders to Salesforce with the Channel Order App
Provide Free Trials of Your AppExchange Solution
OEM User License Guide
PDF

Use Permission Set Licenses to Sell Tier-Based Products

Permission set licenses (PSL) help you monetize specific features and easily create flexible pricing tiers for your second-generation managed packages. By building access controls directly into your app, you make sure that customers only access the exact features they purchase. The Go-To-Market (GTM) app automatically delivers the correct feature-based licenses to your subscribers, which save you valuable time and safely protects your revenue.

To implement and sell feature-based product tiers, use permission set licenses (PSLs) in the GTM app.

Step 1: Understand Packaging Prerequisites.

  1. Build your app as a new package, using Second-Generation Packaging (2GP). If you’re currently using First-Generation Packaging (1GP), migrate your package to 2GP. PSLs can’t be added to a released package.
  2. Don’t rely on upgrade paths. Package upgrades aren’t supported.
  3. Determine your licensing strategy. You can choose between foundational PSLs and optional PSLs.
  4. Test your PSL behavior in a scratch org.

Step 2: Define Your Access Controls.

  1. Embed your access controls directly within your managed package.
  2. Create custom permissions and configure object-level CRUD access.
  3. Associate custom permissions with your PSLs to technically enforce specific pricing tiers.

Step 3: Configure Partner Product Licenses (PPLs)

  1. Access the products from the GTM app.
  2. Connect your Dev Hub to locate and configure your PPLs, which represent the underlying PSLs within your package.

Step 4: Map Licenses to Sellable Products

  1. Create Partner Provision Products (PPPs) to represent the specific tiers or features you want to sell.
  2. Map your technical PPLs and their associated quantities directly to these PPPs. This step bridges your technical package configuration with your commercial catalog.

Step 5: Create and Send Private Offers

  1. When negotiating a deal, create a private offer and select the specific PPPs that match the customer's feature tier.
  2. Specify the quantities and pricing.
  3. Send the offer directly to the customer's org.

Step 6: Use Automated Provisioning.

When the customer accepts your offer and the order reaches its start date, the GTM app automation takes over. The system delivers the correct PSLs to the subscriber’s org, eliminating manual license management and granting the customer access to the features they purchased.