Use Cases
The following use cases demonstrate how Entitlement Sets and license-level feature entitlements in Cryptlex can be used to define product behavior, manage license tiers, and enforce custom limits.
Product tiering
Organizations often offer multiple editions of their product, such as Standard, Pro, and Enterprise, with different capabilities. Entitlement Sets help group relevant feature entitlements into reusable tiers.
For example:
| Tier | Feature Entitlements |
|---|---|
| Standard | basic_export |
| Pro | basic_export, analytics_dashboard |
| Enterprise | basic_export, analytics_dashboard, priority_support, team_sharing |
Licenses are linked to the relevant Entitlement Set, and the application logic checks which features are enabled to control access.
Value-based limits
Feature values can be used to define fixed limits, such as the maximum number of projects or team members, which your application enforces at runtime.
Example:
- Feature:
max_team_members - Value:
5,20, orunlimited - Usage: The application reads the value at runtime and enforces the limit accordingly.
This approach enables per-license limits without requiring new builds or manual configuration. Note that feature entitlements do not track consumption; to meter actual usage against a quota, such as API calls or exports consumed, use meter attributes.
Controlled feature rollouts (beta access)
Entitlements can be used to enable or disable features for a specific group of users, such as beta testers.
Example:
- Features:
beta_dark_mode,ai_autocomplete - Added only to selected licenses
- Application checks for feature presence before enabling UI or functionality
This allows safe, controlled rollouts without the need for separate builds.
Feature trials
Expiry dates on license-level feature entitlements can be used to grant temporary access to specific features without affecting the rest of the license. This is useful for offering feature trials, promotional unlocks, or time-limited access to any premium functionality within your app.
Example:
- Feature:
advanced_reporting - Expiry date:
2026-12-31 - Usage: The expiry information is exposed through the SDK via the
GetFeatureEntitlement()andGetFeatureEntitlements()functions (see Accessing Feature Entitlements) and must be evaluated and enforced by the application itself.
This approach allows targeted, time-bound feature access without creating separate license types or Entitlement Sets and without requiring license reissuance.