Entitlements represent your customer’s contractual right to use, access, or consume services within an agreed scope and time period. In Zenskar, entitlements act as control primitives that govern what a customer can use, how much they can consume, and whether a capability is available, independent of how revenue is billed or recognized.
Important: Entitlements in Zenskar are off-balance-sheet constructs. They do not represent cash, financial liabilities, or actual revenue by themselves. The system tracks usage rights, not monetary claims. Issuing cash refunds for entitlements can create discrepancies in accounting, because Zenskar does not automatically reconcile entitlements with financial transactions.
Zenskar supports multiple entitlement types to reflect different commercial and technical needs. Each entitlement type encodes a distinct kind of right and participates differently in usage evaluation and billing.
Entitlement type
What it represents
How it is measured
Does it get consumed?
Typical use cases
Quantity-based entitlement
Right to consume a measurable amount of a service or product
Units (e.g., API calls, seats, GB)
Yes
Metered usage, quotas, included usage
Credit-based entitlement
Right to consume value expressed in a non-cash unit
Custom currency or credits
Yes
Prepaid credits, platform spend limits
Feature entitlement
Right to access or enable a capability
Enabled / disabled
No
Feature gating, plan differentiation, service access
Each entitlement type serves a distinct purpose:
Quantity-based entitlements control how much of something can be consumed. For example, 1,000 API calls per month, 50 user seats, 500 GB storage, 100 messages per billing period.
Credit-based entitlements control how much value can be consumed, without representing real currency. For example, $1,000 of platform credits, 500 AI tokens, prepaid service credits.
Feature entitlements control whether a capability or service is available at all. For example, SSO access, audit logs, premium API enablement, beta feature activation.
Off-balance-sheet: Entitlements are not financial instruments. They do not automatically appear in accounting books as assets or liabilities. Treat them as usage rights only.
Cash refunds: Users must avoid issuing cash refunds for entitlements. Doing so can create a mismatch between the financial ledger and entitlement balances, potentially resulting in accounting errors.
Time validity: Free units and other entitlements inherit their validity from the pricing model or contract phase. They do not carry independent time semantics.
Navigate to Contracts > Products in the left side panel.
Click on the + CREATE NEW PRODUCT.
On the Add New Product page, add a Free Units node.
Click on the Free Units Name drop-down menu to select an entitlement.
Alternatively, you may create a new entitlement by typing a new name, as shown below:
Optionally, you may click on the Click here to charge overages link to automatically add another free units node that consumes free units to compensate for overages.