Skip to main content
You need resource Owner access to change its billing team. Use the appropriate administration or instance controls for budget settings.

​
Inspect the recorded payer

Open the workspace or dataset settings. Check its billing team before starting substantial work. A collection or source has no separate billing team. Attaching or detaching a dataset does not transfer its payer.

​
Change future ownership

As Owner, select a billing team that you belong to and save. Inspect the saved setting and a subsequent work record. The team need not be a member of the workspace. Billing ownership grants no content access. Earlier usage retains its recorded attribution. When a resource has no billing team, the default team pays. The default team cannot be renamed, assigned members or deleted. An Owner selects another team to move future spend.

​
Set and check limits

For an app instance, set its spending limit per run in settings. Check what the limit covers and test a small run. The app model-spend cap is a soft check between blocks. A block already running can exceed it. Storage and compute need their own applicable controls. Inspect the root task’s allowance, attempts and child work. Revisions and retries consume remaining allowance. A displayed context percentage measures context occupancy, not total cost.

​
Review actual usage

Use Console usage views for the intended user, team, model and workspace. Match the reporting period to the work records. Check inference, allocated compute and retained storage separately. Retried or failed work can have incurred usage. Reusing an existing result adds no new inference call, but retained bytes continue to use storage. A missing price does not mean no usage. Keep measured quantities and pending prices visible until pricing or reconciliation completes. Estimates remain distinct from actual usage and invoices. Review retained evidence obligations before reducing storage. See Understand run outcomes and costs and Retention, deletion and legal holds.