> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-product-catalog/products/add-a-product/product-step-2-features/product-features.md). # Product Features Learn the three feature control types in Zentitle — access control, usage count, and element pool — and how each is packaged into simple UI options like usage with a limit or on/off. ### Features Explained Product features are ways to control your product's components, enabling you to monetize it with maximum flexibility. Zentitle offers three basic "feature types"; these are packaged up into simple options in the UI. * Access Control - Is this feature available in this product, and is it enabled (by default)? * Usage Count - Is this feature usage-based, and is the "overdraft" option enabled? * Element Pool - Is this feature tracked as part of this product's "pool" of usage, and is the "overdraft" option enabled? These are offered for direct setup under the "custom" option in the UI. *** ### Feature control "packages"
#### Usage with limit Feature usage count resets to 0 after a set period. Allows users to consume a feature up to a specified threshold. After reaching the limit, usage may incur additional charges or be blocked. The initial quota is usually included in the core subscription, and overage fees (extra per-unit charges) apply if the limit is exceeded. *e.g., Cloud storage providers: Users get 50 GB/month included, then pay a fee per extra GB.* #### On/Off (boolean) Simple feature selection only. Allows you to enable or disable access to a feature. Used for features where usage is not being metered. *e.g., Typical good/better/best models where the "24/7 Support" feature could be enabled or disabled depending on the edition.* #### Burn down usage with a limit Consumed value is reset to 0 after a set period. Allows users to buy a fixed amount of usage that is consumed, with tracking and visual representation of the remaining license quota or allowable usage over time. *e.g., 1M API calls limit available to use each month, or compute hours that last for 12 months.* #### Metered usage with no limit Feature usage count resets to 0 after a set period. Usage-based feature where cost is tied strictly to actual usage with no predefined caps or blocks—users pay for exactly what they consume in a given period. Costs scale linearly (pay-as-you-go), with no upper threshold on consumption. *e.g., Al writing tools: Users are charged per word generated or credit used, with capacity open-ended as long as payment keeps up with usage.* #### Shared "element pool" with a limit The limit is set and doesn't reset after a period. Allows a group of users to share from a pool of elements/components with a set total limit. Elements are checked out when needed and returned when no longer in use, ensuring that the total shared number of active elements never exceeds the limit. *e.g., Customers can have up to 3 custom domains set up and can always remove one to free up a slot to add another.* #### Usage with Rate Card Feature usage count resets to 0 after a set period. Allows you to combine metered usage features into one "currency". The rate card allows for varying "credits" values for different features to be combined into an offering. *e.g., ChatGPT: Buy credits and spend them on features like Deep Research, GPT-5 Thinking, and Advanced Voice, each with its own "credit" value.* #### Custom All three types in a simple UI as shown above. *** #### Access Control {% hint style="info" %} Access control is a simple boolean on/off switch for your feature controls; this easily enables you to tag all your key features and switch them on or off based on various scenarios like offering different "editions" of your product, etc. {% endhint %} #### Usage Count {% embed url="" %} {% hint style="info" %} An entitlement can have one or more ‘counter’ features. The usage counter tracks usage over time and can be easily reset to zero. {% endhint %} For example, you may have a 1-year subscription that provides 1000 report runs over the year. The feature would track how many reports have been run so far (with the application deducting 1 from the count each time a report is run). {% hint style="info" %} Once you have an entitlement set up using usage counters, you may need to manage the usage levels on these advanced features. In certain cases, you may wish to leave an entitlement with a client in place and adjust its usage levels rather than offering a new entitlement with higher usage, etc. See how to reset[ the usage count on an entitlement.](/zentitle2-docs/ui-entitlements/managing-entitlements/resetting-the-usage-count-manual.md) {% endhint %} #### Element Pool {% embed url="" %} {% hint style="info" %} Element Pools represent a concurrent aggregate count of some measure. {% endhint %} For example, let’s say there is a storage management cluster, and the business model charges for the aggregate storage under management across the cluster. Each node would check out from the element pool the quantity of storage it was managing (50TB, 100TB, etc.), and the licensing would enforce that the aggregate amount of licensed storage was never exceeded. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nalpeiron.com/zentitle2-docs/ui-product-catalog/products/add-a-product/product-step-2-features/product-features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.