Settings: Entitlement catalog
Define the features and credit packs you sell: a name, how long it lasts, how many credits it carries. Everything else is giving them out.
Open it now:Settings, Entitlements
Add an entitlement
Press Add entitlement. Up to 100 per application.
| Field | Meaning |
|---|---|
| Name | Lowercase letters, digits, dot, dash and underscore, up to 40 characters, for example pro or export.pdf. It is what your code asks for, and it cannot change afterwards. |
| Validity period | An amount of hours, days, weeks, months or years, or lifetime. It starts when the key is first used, or when you give it or the customer redeems it. A month is 30 days and a year 365. |
| Credits | Optional. Empty makes a plain on/off feature. A number makes a counter that starts with that many credits; your program spends them and the server refuses a spend past zero. A counter with no number counts usage without a limit. |
The list
Each row shows the name, its duration, its credits, how many licenses and accounts hold it (Held by) and, for counters, how many credits were spent in total (Spent). Edit changes the duration and credits; Delete removes the entitlement and every grant of it.
A change applies to what you give from now on. Customers who already hold the entitlement keep what they have, so raising the credits does not top anyone up.
Where they are used
- Pick them when you generate licenses or accounts.
- Give them to existing customers one by one or in bulk: see Entitlements.
- Check and spend them from your program: see Entitlements in the SDK.
Was this page useful?