Team model aliases and presets, and denied models and providers
Send org/fast as the model and define once, in Directives, what it runs: a model id, or a preset with fallback models and defaults for temperature, top_p, max output tokens and reasoning effort. Swap the model behind an alias without a redeploy. deniedModels and deniedProviders block a model or provider whatever the allowed lists say.
Aliases are set on the team or a project, in the new Aliases group of the Directives table; a project's alias replaces the team's of the same name. They resolve before anything else, so allowed and denied lists, ZDR, no training and certification apply to the model an alias names. A preset's defaults fill only what the request leaves out, and its fallback models stand in for routing.fallbackModels on its requests.
Receipts keep what you sent (model_requested is org/fast) and name the model it ran as. GET /v1/models lists your aliases with owned_by: "org" and alias_for, and an alias nobody defined returns 400 invalid_request. With mixed-model sessions, suggestions are for the model the alias names.
deniedModels takes model ids or vendor/* for every model of a vendor, deniedProviders provider ids. Denials from every level add up and win over allowedModels and allowedProviders; set them in the Access group, as JSON, or with the management API, where one alias is the set path aliases.org/fast.
More in Directives: Model aliases.