Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hyperline.co/llms.txt

Use this file to discover all available pages before exploring further.

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:
SourceDescription
Default valueThe fallback value configured on the feature in the catalog.
Product grantA value granted by a product included in the customer’s active subscription.
Customer overrideA value set directly on the customer. Overrides product grants and the default value.
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.

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:
TypeUse forExample
BooleanAccess that is enabled or disabled.SSO, premium support, white-labeling, HubSpot integration.
NumberLimits, quotas, or numeric entitlements.Included seats, API calls, projects, storage in GB.
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.
ResolutionBehaviorUse when
MaximumUses 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.
SumAdds the default value and product grant values. Customer overrides win.Multiple products should stack together, such as included seats or usage quotas.
ReplaceUses a product grant value instead of the default value. Customer overrides win.A product should define the entitlement value directly.

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. Set the Default value.
  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.

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.
  6. Click Save.
When the product is included in a customer’s 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 to see the resolved entitlements for that customer. Each row shows the feature name, resolved value, and a source hint explaining where the value comes from:
  • Default value means the value comes from the feature catalog.
  • Granted by product means one or more subscribed products grant the feature.
  • Overridden for this customer means a customer-specific value is applied.

Override a customer entitlement

Use customer overrides for exceptions that should apply only to one customer, such as a temporary access extension, a negotiated limit, or a support-approved exception.
  1. Open the customer page.
  2. In Entitlements, click Edit.
  3. Update the feature value.
  4. Optionally add a reason and an expiration date.
  5. Click Save override.
Customer overrides replace the resolved value from product grants and the feature default. Reset the override to return to the value calculated from the customer’s products and the feature catalog.
Customer overrides are customer-specific exceptions. Use them when the customer should intentionally differ from the product configuration.

Next steps