How entitlements are resolved
An entitlement is the resolved value of a feature for a customer. Hyperline calculates it from three possible sources:| Source | Description |
|---|---|
| Default value | The fallback value configured on the feature in the catalog. Optional — features can be created with no default. |
| Product grant | A value granted by a product included in the customer’s eligible subscription. |
| Customer override | A value set directly on the customer. Overrides product grants and the default value. |
active or paused. Paused subscriptions keep product-granted access, while other subscription statuses do not contribute product grants.
Features without a default value
Specifying a default is optional. A feature can be created with no default value for both boolean and number types. When a feature has no default:- Customers receive no resolved entitlement unless a product grant or a customer override provides one.
- No source is displayed for the feature on the customer Features tab until a grant or override is set.
- Use this when access should be explicitly granted per product or per customer rather than assumed by default — for example, a beta capability that only certain plans or customers should ever see.
Example 💡
A HubSpot integration feature has a default value of disabled. The Growth plan product grants the feature as enabled. Customers subscribed to Growth receive the integration automatically, while a customer override can still enable or disable it for a specific customer.
Feature value types
Features can use two value types:| Type | Use for | Example |
|---|---|---|
| Boolean | Access that is enabled or disabled. | SSO, premium support, white-labeling, HubSpot integration. |
| Number | Limits, quotas, or numeric entitlements. | Included seats, API calls, projects, storage in GB. |
| Resolution | Behavior | Use when |
|---|---|---|
| Maximum | Uses the highest value across the default value and product grants. Customer overrides win. | Multiple products can increase a limit, but the customer should receive only the largest grant. |
| Sum | Adds the default value and product grant values. Customer overrides win. | Multiple products should stack together, such as included seats or usage quotas. |
| Replace | Uses a product grant value instead of the default value. Customer overrides win. | A product should define the entitlement value directly. |
Create a feature
- Go to Catalog > Features.
- Click New feature.
- Enter the feature Name and, if needed, an Internal description.
- Enter a stable Code. Use an API-safe key such as
sso,hubspot_integration, orincluded_seats. - Choose the value Type:
- Boolean for enabled or disabled access.
- Number for quotas or limits.
- For number features, choose the Resolution strategy.
- Optionally toggle Default value on and set the value. Leave the toggle off to create the feature with no default — customers will only receive an entitlement when a product grant or override provides one.
- Click Save feature.
Grant features from products
After a feature is created, add it to the products that include that capability or limit.- Go to Catalog > Products.
- Open the product that should grant the feature.
- In Entitlements, click Add feature.
- Select the feature from the catalog.
- Keep the default value or open the row to set a product-specific value. If the feature has no catalog default, you must provide an explicit value for the product grant to save.
- Click Save.
Entitlements do not create invoice lines or change the product price. They describe access granted by products that are already billed through subscriptions, quotes, or invoices.
Review customer entitlements
Open a customer page and select the Features tab to see the resolved entitlements for that customer. Each row shows the feature name, resolved value, and a tag indicating where the value comes from:| Tag | Meaning |
|---|---|
| Default | The value comes from the feature catalog. |
| Product | The value is granted by one or more of the customer’s subscribed products. Hover the tag to see which subscriptions contribute. |
| Override | A customer-specific value is applied on top of product grants and the default. |
The Features tab is available to members with the
entitlements_update permission on workspaces that have entitlements enabled.Override a customer entitlement
Use customer overrides for exceptions that should apply only to one customer, such as a negotiated limit, an early access grant, or a support-approved exception.- Open the customer page and select the Features tab.
- Find the feature in the table and open the row’s action menu.
- Click Edit to open the override modal.
- Update the Value and, optionally, add a Reason to record why the override exists.
- Click Save.
Grant a feature to a customer
You can also grant a feature directly to a customer, even if no subscribed product includes it.- Open the customer page and select the Features tab.
- Click Grant feature and pick a feature from the picker.
- Set the Value and, optionally, a Reason.
- Click Grant feature.
Next steps
- Create billable catalog items in Products and prices.
- Add products to customers when you create a subscription.
- Use customer segments to group customers with similar access or commercial rules.

