Different company offers. Not different versions of your app.
Offer a Premium library to one company and more features to another. Your app checks the capability; your team shapes the offer.
Name the feature. Choose how to sell it.
Give each feature a stable Entitlement key: Premium content, analytics or exports. Include it in licenses while keeping the feature separate from plans, seats and users.
For example, premium can provide the same content through a club license or a company agreement. A new package can use the same feature check.
Losing one access path is not always losing access.
One person can receive a feature through several licenses. Ending one agreement can leave another valid path open.
- Overlapping licenses
- Two licenses include analytics? Releasing one seat preserves access while the other license still provides it.
- Personal and company access
- Your backend can combine company access with a personal subscription. Both sources can coexist under your product’s rules.
Your backend asks. Your application enforces.
A seat connects an existing user to a license and its included features. BusinessMode tracks those access sources and returns the current answer.
Check the stable feature key when someone uses the capability. Your application enforces the result, alongside any personal-subscription rules. Use existing user IDs and keep credentials server-side.
The API reference defines each request and response. Package names can change without spreading new checks through your application.
Make the next company offer without another app variant.
Choose a feature, include it in an agreement and connect the access check. Start with the Quickstart.