Entitlements & templates
An entitlement is the central record: a customer’s grant to a product’s features, under a plan and a set of policies. Everything upstream (products, features, plans, bundles) exists so you can issue good entitlements; everything downstream (activation, sessions, usage) flows from them.
Two independent states
Section titled “Two independent states”- Publication lifecycle —
Draft → Published → Disabled → Archived. Your editorial control; only a published entitlement can be activated. - Subscription status —
Pending,Trialing,Active,Paused,Expired,Canceled. The runtime state the customer experiences, computed from the entitlement’s policies and dates.
Features are a snapshot
Section titled “Features are a snapshot”When a product is added to an entitlement, its features are copied in — a snapshot of the product as it is at that moment. The entitlement keeps its own copy, so later edits to the product don’t change a live customer’s grant. What a customer effectively has at any moment is that snapshot, plus any active bundle grants, plus the values from the assigned plan, resolved together.
Policies
Section titled “Policies”Policies decide how the entitlement may be activated and for how long — they combine:
- Seat allocation — fixed or floating seats, with a lease and offline grace.
- Trial — a trial window, optionally starting on first activation.
- Time-restricted — valid between two dates, or for a period after first use.
- Subscription — recurring periods with renewal and expiry.
Templates
Section titled “Templates”An entitlement template is a reusable blueprint — a captured shape (products, features, policies) you can stamp out repeatedly. Bundles build on templates so a whole offering can be granted in one step. You can also tag an entitlement with an external reference (e.g. a CRM or billing id) to keep it linked to your other systems.