Skip to main content
Model access lets you define the part of Opper’s model catalog that your organization can use. Start with an organization allowlist, then narrow it for projects with stricter requirements.
Model access restricted to four providers with a project override
With no model-access rule, every model in the catalog is available.

​
Build an organization allowlist

Select Set an org allowlist, then filter the catalog by any combination of these fields: A model must match every field you set. Leave a field empty when you do not want to filter on it. Blocked providers always take precedence. The match counter updates as you edit. Select it to review the exact models that will remain available before you save.
A dialog listing the catalog models that match the allowlist
If the same provider appears in both Providers and Blocked providers, the rule cannot be saved. The pickers hide already-selected values to help prevent that conflict.

​
What model access covers

Model access applies to LLM and embedding calls. When a call requests a disallowed model, Opper returns an error that identifies the model and the rule it failed. Opper does not silently switch to a different model. Model access does not currently apply to:
  • Image, speech, and video generation. Use spend limits to bound their cost.
  • Virtual and router models, which filter the variants they can use separately.
Route rules must point to a model that the same scope can use. If an allowlist change would invalidate an existing route, Opper asks you to resolve the conflict before saving.

​
Narrow access for a project

Select Narrow model access for a project to add an override. A project override intersects with the organization rule: it can remove access, but it cannot restore a provider, region, country, or model that the organization rule excluded. The override summary shows the effective result, not just the fields you added:
While you edit an override, values unavailable at the organization level are dimmed.
A project provider picker with values excluded by the organization rule dimmed
To make one of those values available, broaden the organization rule first. You can edit both levels in the same draft and save them together.
An override can leave a project with 0 available models. Opper warns you but allows the save because denying all model calls may be intentional.

​
If older organization rules exist

The runtime uses only the newest enabled organization allowlist. Older organization allowlists have no effect and do not intersect with it. Rules shows the active allowlist and tells you when older rules are still present so you can remove them. Project overrides still intersect with the active organization allowlist.

​
Model access under Zero Data Retention

When Zero Data Retention is enabled, model access is locked to providers with zero-retention agreements. The fields become read-only and the counter shows the models available from those providers.
Model access locked to providers eligible for Zero Data Retention
Set broad requirements, such as “EU providers only,” at the organization level. Use project overrides for workloads that need an even smaller model set.