Team billing, spending, and seats
Team Management separates the billing account from AI and cloud spending policies. A project action can be blocked by any applicable account, entitlement, or policy even when the project itself is accessible.
Billing account
Open Billing to inspect the account associated with the organization, its status, and available billing details. Only authorized billing roles can update or replace that association. Verify the organization and account before saving a change because subsequent usage may be charged to the newly selected account.
Spending controls
Open Spending to review configured limits or controls for Agent and cloud usage. A policy can allow, warn, or block operations according to the organization configuration. When a run is denied, read the policy reason and ask an administrator to adjust the approved limit; repeatedly resubmitting the same request does not change the policy.
Seat capacity
Review builder and viewer capacity, occupied and reserved counts, and any scheduled capacity change. Increase capacity only after confirming the required count and organization billing impact. A reservation can be held for a pending invitation; revoke an unused invitation to release it when the interface allows.
Budget versus personal credits
Organization spending controls and an individual's credits are separate ledgers. Check which identity is active and which billing account funds the project before starting metered work. A team member may not be able to see or edit financial details even if they can use the project.