Subscriptions
A subscription links a customer or organization to a service plan. It stores entitlement state; the panel does not charge payment cards or run your external billing system. Customer suspension is a separate operational action.
Managing a subscription
Open the Subscription section on a customer detail page or organization edit form. Manage subscription opens the editor for the plan, status, expiry, external reference and metadata. There is no separate subscriptions list page.
| Field | Meaning |
|---|---|
| Owner | Exactly one customer or organization |
| Plan | Customer-kind for a customer; resource-kind for an organization |
| Status | active, suspended or expired |
| Expiry | Optional timestamp used by the expiry worker |
| External ID | Your billing system's reference |
| Metadata | Additional integration data; keep secrets out of this field |
The subscription API is admin-protected. Changes also require subscriptions.manage; an assigned permission alone does not bypass the admin route guard. Status transitions are audited. See the API overview for authentication before building an integration.
Operational limits
Changing a subscription does not collect payment, stop containers, or resize existing services. Use customer suspension when you need the separate account-and-service action. A plan reduction is not an automatic resource reclamation operation; review current allocation before applying it.
Owner creation and subscription creation have different failure handling across customer and organization paths. Check both the owner's state and its subscription after a failed request. Do not infer a valid entitlement from the owner row alone.
A subscription has one plan. This guide makes no release-date promise for add-ons, payment processing, over-quota notifications or a dedicated list page.