AI Runtime has three levels, and knowing which one you are acting on explains most access questions.
Organization
The top level, backed by Clerk. It owns members, roles, the audit log and the commercial Agreement. An Organization can hold several Workspaces, and the Organization switcher in the console rail changes scope for the whole application.
Workspace
The isolation unit. Pools, API keys, budgets, requests and usage evidence belong to exactly one Workspace, and Workspaces never see each other’s traffic. Creating one is an Organization admin action, and the Agreement’s limits decide how many an Organization may have.
Environment
production or development, selected for the whole console scope. API keys are issued for one
Environment, so a development credential cannot spend production traffic.
Home Cloud
The customer plane that serves a Workspace: Google Cloud, AWS, Azure or the shared edition. It comes from the Agreement, not from the Workspace, and every projection in the console is loaded against that exact scope. A key issued for one Home Cloud is refused by another.
Switching scope
The console keeps one global scope: Organization, Workspace, Environment. Changing it reloads every projection. If the new scope cannot be loaded, the console keeps the last confirmed scope and tells you why instead of showing another Workspace’s numbers.