Tenant Resource Allocation

Tenant Resource Allocation assigns Credit, concurrency, and account resources to tenants belonging to the current customer. It applies to standalone public-cloud and private deployments. Users with resource management permission in the customer operations tenant can open System Management → Tenant Resource Allocation, with Resource Overview and Allocation, Tenant Status, and Allocation Records sections.

Resource overview and allocation

The overview shows total, allocated, and remaining Credit, concurrency, and account resources, grouped by customer and model. Accounts and concurrency inherit the order's expiration date. Credit is allocated by order resource package, retaining each package's model, source, and validity period.

• All resources have a model attribute and can be assigned only to tenants using the same model. Official-model resources cannot go to private-model tenants, or vice versa.
• Each allocation must distribute the full amount. Account and concurrency allocations must total the corresponding model pool's capacity; monthly Credit allocations must total the package's per-cycle amount. Changing one tenant's allocation adjusts others using the same model. Values cannot be negative, and account allocations cannot fall below enabled account counts.
• Newly received resources show an unallocated quantity. Use Allocate New Resources to distribute the full increment while preserving existing allocations.

Credit allocation

• Monthly allocation: Change the monthly plan starting next cycle. Adjustments leave current-cycle quotas and historical disbursements unchanged and do not release future months' Credit early.
• One-time allocation: View allocated, consumed, and remaining Credit per tenant. Remaining Credit means all unconsumed balance, including amounts already assigned to tenants. Redistribute it among tenants using the same model without changing consumption totals or package validity. Exhausted packages cannot be redistributed.

Concurrency allocation and activation

Concurrency follows the allocation unit configured for the environment. For a unit of 5, valid allocations are 0, 5, 10, 15, and so on. Initial allocations, reallocations, and new-resource allocations all follow this unit.

Concurrency changes do not take effect immediately after saving. If an adjustment reduces capacity, the new allocation completes after running tasks in affected tenants finish and release concurrency.

Tenant status and allocation records

• Tenant Status: View each tenant's model, account and concurrency quotas, allocated Credit, and associated packages. Tenant details trace source orders, package validity, and monthly allocation plans.
• Allocation Records: Track order associations, account, concurrency, and Credit allocations, and monthly plan changes. Records include operator, time, resource type, affected tenants, before-and-after quotas, and effective time.