LicenPro
DocumentationPlatformFeatures & entitlement sets

Features & entitlement sets

Define capabilities, bundle them into SKUs, assign sets to licenses, and enforce them in the SDK at runtime.

Features are atomic toggles or capabilities (e.g. export_pdf, max_projects). Entitlement sets group features for assignment to licenses so you ship packages without recompiling for every SKU.

Configuration lifecycle

  1. Define features on product Features tab (…/features).
  2. Bundle into entitlement sets on Entitlement Sets tab (…/entitlements).
  3. Assign optional set when creating/editing a license (wizard step 1 or details).
  4. Distribute license.bin—signed payload includes entitlement material.
  5. Enforce in app via SDK FeatureManager; optional FeatureUsageTracker for metering.

Features tab

Product owners define the capability catalog before bundling SKUs. End users and non-owners do not see this tab.

  • Feature key — stable identifier referenced in code (FeatureManager.IsEnabled("key")).
  • Display name & description — operator documentation and support context.
  • Assign to groups — blue tags (e.g. Groub1, Groub2) pre-group features for entitlement set authoring.
  • Create Feature — adds a row to the searchable table with created-on date and actions menu.
  • Type / default — boolean gates, numeric limits, or structured values per your product model.

Design tip: prefer fewer, well-named keys over dozens of overlapping toggles—customers receive entitlements through sets, not individual feature rows.

Click image to open full-resolution preview.

Entitlement Sets tab

Bundle features into reusable packages operators attach at license creation.

  • Create Set — name, description, and linked release tags (1.0.0, 1.0.3, …).
  • Features column — count of capabilities in each set (e.g. “3 features”).
  • Add features — pick from catalog with per-feature values (enabled, limits).
  • License wizard — saved sets appear in the step 1 dropdown.
  • Edit impact — changes affect new issuances; existing signed licenses keep old material until re-issued or refreshed online.
Click image to open full-resolution preview.

Runtime enforcement

  • Offline — entitlements inside signed license.bin; SDK verifies signature then reads feature payload.
  • Online refresh — validation or feature endpoints may update entitlements when subscription changes mid-term.
  • Usage tracking — optional counters shipped to telemetry routes (Telemetry API).

Roles

Only product owners and system Admin see Features and Entitlements tabs. Members consume entitlements through licenses they hold—not author them.

SDK: Features & usage · REST catalog · Licenses (vendor) · Products