Skip to main content
In Tirdad, managing customer access to features is done through entitlements. An entitlement defines which features a customer can access based on their subscription plan. This ensures that each customer receives the correct level of access, allowing precise control over feature availability and usage limits. Linking Features to Plans through Entitlements
  • Open Product Catalog → Plans and choose the plan to which you want to link features.
  • Open the plan’s Entitlements tab.
  • Click Add to add the desired features to the plan.
    Add Entitlement
  • Configure access parameters, including usage limits, permissions, and other relevant settings.
    Configure Entitlement
  • Click Add under the feature, then Save, and the entitlements will be applied to all customers on this plan.
Configuring Entitlements for Different Feature Types
  • Boolean Features
    • Selecting a Boolean feature grants or restricts access for customers on this plan.
    • No further configuration is required: selecting it adds it straight to the Added list. Click Save.
      Boolean Entitlement
  • Metered features
    • Setting the Value
      Metered Entitlement Value
      • Choose the Value Type: Quantity (meter units) or Amount (currency).
      • Enter the Value: the usage a customer is allowed in each window.
      • If there is no cap, select Unlimited.
    • Usage reset
      Metered Usage Reset
      • Usage resets sets how often the value refreshes: Every billing period, Hourly, Daily, or Weekly.
      • A reset shorter than the billing period is independent of the billing cycle. Advanced holds Window starts and Stacking; see Entitlement grants.
      • When enabled, usage resets to zero at the specified interval, regardless of when the billing cycle occurs.
💡 Example: A plan is billed monthly, but API call limits reset every day. Setting Daily ensures that users get a fresh allocation of calls each day.
  • Soft Limit vs. Hard Limit The Tirdad console has no Soft Limit switch: usage beyond the value is billed at the plan’s usage price, and the entitlement.grant.exhausted webhook fires when a window’s value is used up. Once a customer reaches their allocated limit, your application can handle additional usage in two ways:
    • Soft Limit (Overage Allowed)
      • Customers can exceed their limit.
      • Excess usage may be charged separately (based on pricing rules).
      • Common for pay-as-you-go models.
💡 Example: A GPT API plan allows 50,000 tokens/month, but if exceeded, additional tokens are charged $0.10 per 1,000 tokens.
  • Hard Limit (Strict Cap)
    • Customers cannot exceed the limit.
    • Once they reach their limit, requests are blocked.
    • Typically used for free tiers or strict allowances.
  • Static Features
    Static Entitlement
    • Instead of setting limits, define a custom value.
    • Example: 24/7 support, premium customer service, AI model access.
    • Customers will see these benefits listed as part of their subscription.
The linked features are now associated with the plan, and subscribers will have access according to the configured entitlements.