Skip to main content
Features represent the product capabilities, access rights, or usage limits that customers receive outside of billing. They help your team track what each customer is entitled to use, based on the products they have and any customer-specific override. Use features when you need to manage access such as SSO, premium integrations, included seats, API limits, or support tiers. Products still define what you sell and bill. Features define what access or limit that product grants.

How entitlements are resolved

An entitlement is the resolved value of a feature for a customer. Hyperline calculates it from three possible sources: Customer overrides always take priority. If no customer override exists, Hyperline uses product grants. If no product grant changes the value, Hyperline uses the default value from the feature catalog. Product grants contribute to entitlements when the subscription that includes the product is 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: Boolean features do not require a resolution strategy. If a product grant enables the feature, the customer receives access unless a customer override changes the value. Number features use a resolution strategy to combine the default value and product grants. When a number feature has no default value, resolution falls back to the product grants and customer overrides only. Maximum and Sum ignore the missing default and compute across product grants alone, and Replace uses the product grant value directly.

Unlimited number entitlements

A number entitlement can be set to Unlimited to grant uncapped access instead of a finite limit. Turn on the Unlimited toggle next to the value when you set a product grant, a customer override, or a direct customer grant. Unlimited applies to the entitlement value only. The feature’s catalog default value always stays a plain number (or empty) — it cannot be set to Unlimited. Unlimited interacts with the resolution strategy as follows: As with any number feature, a customer override takes priority over product grants and the default value, so an Unlimited override grants uncapped access regardless of the product grants.

Example 💡

An API calls feature has a default limit of 10000. The Enterprise plan product grants the feature as Unlimited. Customers on Enterprise receive uncapped API calls, and a customer override can still set a specific number for a single customer.

Create a feature

  1. Go to Catalog > Features.
  2. Click New feature.
  3. Enter the feature Name and, if needed, an Internal description.
  4. Enter a stable Code. Use an API-safe key such as sso, hubspot_integration, or included_seats.
  5. Choose the value Type:
    • Boolean for enabled or disabled access.
    • Number for quotas or limits.
  6. For number features, choose the Resolution strategy.
  7. 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.
  8. Click Save feature.
Use codes that match how your product team refers to access internally. Stable codes make reporting and integrations easier to maintain.

Archive, recover, or delete a feature

Features have a lifecycle in the catalog. Archive a feature when you no longer want it granted to new products or customers, and delete it when it is no longer needed at all. Open a feature from Catalog > Features and use the Actions menu: The archive state can only be changed through these actions. It is not editable from the feature edit form.

Filter features by status

The Features list has a Status filter with three values:
  • Active — the default view. Shows features that are not archived.
  • Archived — shows only archived features. Use this view to find and recover a feature.
  • All — shows every feature regardless of status.

Archived features on products and customers

Archived features remain visible where they are already in use:
  • Product Entitlements panels continue to show archived features that are granted by the product, so you can still see and adjust their values.
  • Customer Features tabs continue to show archived features that contribute to the customer’s resolved entitlements.
You cannot add an archived feature to a new product or grant it as a new customer override — recover it first, or add a different feature.

Manage feature lifecycle from the API

The same actions are available on the REST API. Use them from your own tooling or automation when you manage the feature catalog outside the app. See the Archive a feature and Unarchive a feature reference for request and response details.

Grant features from products

After a feature is created, add it to the products that include that capability or limit.
  1. Go to Catalog > Products.
  2. Open the product that should grant the feature.
  3. In Entitlements, click Add feature.
  4. Select the feature from the catalog.
  5. 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. For number features, turn on Unlimited to grant uncapped access instead of a finite value.
  6. Click Save.
When the product is included in a customer’s eligible subscription, its feature grants contribute to that customer’s resolved entitlements.
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:
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.
  1. Open the customer page and select the Features tab.
  2. Find the feature in the table and open the row’s action menu.
  3. Click Edit to open the override modal.
  4. Update the Value and, optionally, add a Reason to record why the override exists. For number features, turn on Unlimited to grant uncapped access.
  5. Click Save.
To remove an override and let Hyperline recalculate the value from product grants and the feature default, open the row’s action menu and click Reset.

Grant a feature to a customer

You can also grant a feature directly to a customer, even if no subscribed product includes it.
  1. Open the customer page and select the Features tab.
  2. Click Grant feature and pick a feature from the picker.
  3. Set the Value and, optionally, a Reason. For number features, turn on Unlimited to grant uncapped access.
  4. Click Grant feature.
The granted feature appears in the table with the Override tag and behaves like any other customer override.
Customer overrides are customer-specific exceptions. Use them when the customer should intentionally differ from the product configuration.

Next steps