Add-ons
The current commercial model does not have standalone AddOn or TenantAddOn records. Extra capacity is purchased as priced Limit lines in a CustomPlan or LimitIncrease order.
What Are Add-ons?
The active Limit catalog can price additions such as:
- Additional Storage — Increase your file storage quota beyond what your base plan includes.
- Extra Integration API Clients — Add more API client slots if your integrations require multiple concurrent connections.
- Extended Response Capacity — Increase the number of survey responses your plan can collect.
An available
LimitPrice, market/currency price, and catalog bounds are required. EachLimitPricerow can carry its own discount percentage, which applies only to that limit's own order lines: a limit discount is never inherited from a plan, and a plan duration discount is never applied to a limit line. There is still no add-on entity and no add-on-specific discount. “Add-on” is a user-facing description here, not a separate current product entity.
How Add-ons Are Configured
Use the unified order workflow:
- Open
/Tenant/Orders/Create. - Choose Limit Increase for an existing subscription, or Custom Plan for a tailored plan.
- Select the desired Limit values and submit the draft order.
- A Platform Admin reviews the order. Approved capacity is applied only after the full invoice payment is recorded or its proof is verified.
Viewing Your Active Add-ons
Capacity purchases are visible through the owning records:
- Open
/Tenant/Ordersto view order type, status, and priced lines. - Open
/Tenant/Invoicesto view the matching invoice lines. - Open
/Tenant/Subscriptionto view the applied entitlement snapshot after payment verification.
Add-on Invoicing
Each commercial order owns exactly one invoice. Purchased capacity appears as immutable InvoiceItem line snapshots on that invoice; it is not attached to a recurring add-on record.
Removing an Add-on
The current LimitIncrease settlement validates increases; it is not a self-service decrease/removal flow. Use a plan-change order or contact a Platform Admin for a separately agreed change. No automatic next-cycle removal behavior is implemented.