Billing and Change Requests
Review invoices, payment setup, automatic collection, limits, and privileged requests.
Use Billing for invoices, payment setup, cost allocation, and collection mode. Use Change Requests when a desired action is outside your current tenant policy bounds.
Billing workflow
| Task | Portal action |
|---|---|
| Check trial and billing readiness | Open Billing. |
| Register a payment method | Start payment setup and complete the provider link. |
| Pay an invoice manually | Use the invoice payment action where available. |
| Enable automatic collection | Toggle automatic collection after payment setup is complete. |
| Review invoice history | Open invoice details and payment attempts. |
| Understand cost drivers | Compare usage/cost allocation with namespace and resource changes. |
Automatic collection should be an explicit tenant choice. If disabled, invoices remain payable manually where payment links are available.
Change requests
Create a request when the portal shows that a change is outside current self-service bounds:
- resource quota or storage quota increase;
- allowed egress expansion;
- exposure hostname or ingress-class expansion;
- operator capability enablement;
- assignment mode change;
- backup/default protection policy change.
Requests are auditable. Some can be auto-approved inside policy bounds; others need operator review.
RPC/function map
| Portal action | gh0stplane surface |
|---|---|
| Load billing state | GetCustomerBillingView |
| Start payment setup | StartBillingPaymentSetup |
| Refresh payment setup | RefreshBillingPaymentSetup |
| Enable/disable automatic collection | UpdateBillingAutomaticCollection |
| Start manual invoice payment | StartBillingInvoicePayment |
| Load change request workspace | GetTenantChangeRequestWorkspace |
| Preview request | PreviewTenantChangeRequest |
| Create/cancel request | CreateTenantChangeRequest, CancelTenantChangeRequest |
| Operator approval flow | ListTenantChangeRequests, ApproveTenantChangeRequest, RejectTenantChangeRequest |
Before requesting more
Include a clear reason and concrete desired values. Good reasons explain the application, resource impact, and urgency, for example: "Immich import needs 200 Gi storage and 4 Gi memory for initial library processing."
Questions or ready to get started?
Talk to us