-
Notifications
You must be signed in to change notification settings - Fork 0
Gen3 Admin Financial Controls
- Open Financial Controls.
- Review base infrastructure fee fields separately from usage pricing.
- Update model pricing tables when Models catalog changes.
- Lock or document explanatory notes before saving billing changes.
Financial controls affect chargeback and budgets—separate base fees from variable usage to avoid silent policy drift.
Financial Controls is the active Gen 3 billing-policy workspace. It combines billing enablement, budget posture, model pricing, storage pricing, and allocation management on one Control Panel route.
The live page includes:
- billing status review
- billing enable/disable control
- budget and enforcement policy
- model-pricing configuration
- storage-pricing configuration
- allocation creation and review
Use this section to confirm whether billing is enabled and whether the deployment has the license posture needed for billing-aware workflows.
Use budget settings to define warning, critical, or hard-stop posture and the general enforcement model for the deployment's infrastructure-credit or budget behavior.
This section controls the prices attached to configured models. Keep it aligned with the actual provider catalog so observability and budget posture remain meaningful.
Deep-dive runbooks:
- Model Pricing workspace — statuses, online reset, CSV import/export, capability and compound rows
- Provider rate cards — vendor list-price URLs and mapping into input/output per 1M tokens or unit pricing
Use storage-pricing controls when the deployment tracks retained content cost as part of billing posture.
See Storage pricing for dataset/document GiB-month meters and tenant Billing verification.
Use allocations to divide or label spending posture in a more structured way than a single shared pool.
- Confirm billing is enabled only when the deployment is ready for it.
- Review the budget policy.
- Update model prices after any material provider-catalog change.
- Review storage-pricing assumptions.
- Create or adjust allocations only after the baseline policy is sound.
- It does not activate the enterprise license. Use License.
- It does not manage the underlying inference provider connectivity. Use Models.
- Change pricing soon after provider or model changes so analytics stay trustworthy.
- Treat enforcement posture as an operational policy decision, not just a UI toggle.
- Review tenant-facing billing analytics after major policy updates to confirm the outcome is understandable to tenant users.