Control model access

Choose which models the organization and each project can use, and find why a member cannot see one.

  • Lesson 3 of 6
  • Checked Nov 11, 2026

About this lesson

Why a model can be missing, and how admins choose the models: the organization's list and its switches and filters, a project that can only narrow it, the Model Hub for new models, and your own provider keys under External Keys. The models and settings in this lesson are as of November 2026.

See moreSee less
  • Every plan runs every model; on Enterprise, a model shows only if the organization list and the project list both allow it.
  • Build an approved list in Organization > Models, and narrow it per project.
  • Run supported providers on your own API keys, under External Keys.
Step by step in the web app (9 steps)Hide the steps
  1. Check the picker's filters first

    In the Model panel, click the filter icon next to Search by keyword: Input type on Any input, the budget and speed filters clear. The tabs under the search (ALL, image, video, audio, 3D) filter by output too.

  2. Open the organization's model list

    Pill › the gear next to the organization › Models. It holds Project overrides, two switches, and the list with Disable All Models, Enable All Models, Search, filters and an Active switch per model.

  3. Decide what happens to new models

    Automatically enable new models makes a new model ready at launch; turn it off if every model must be reviewed. Display disabled models (admins only) keeps disabled models visible to admins.

  4. Filter the list to fit your policy

    Filter by Privacy, Category, Capabilities, Providers, Sub Processors, Maintainers, Data Processing, Enterprise Status or Tags. Most security reviews start from Enterprise Status › Ready.

  5. Build an approved list

    Click Disable All Models, then switch on only the models you allow in the Active column. With a filter on, the list shows only the matching models; clear it with its x.

  6. Narrow the list for one project

    Project › Models can turn off more models, never turn on one the organization blocked; each shows Inherited until changed. A good pattern: a wider organization list, approved models only in production, and a sandbox for new ones.

  7. Add your own provider keys

    Organization › External Keys, pick a provider (OpenAI, Anthropic, GCP, xAI, Bytedance, Tencent, Tripo AI or ElevenLabs), Add Credentials, paste the key in API Key and click Save credentials. Make sure it has generation permissions.

  8. Know who bills what

    Your provider bills each generation on your key; Scenario still charges the fees on the Minimum Post-Processing Fees card. Your keys don't cover training, workflows, storage or Scenario's own models.

  9. Give a project its own key

    Project › External Keys (or Go to Project View from the organization page) takes a key that wins over the organization's. Until you add one, the provider shows Inherited.

Read the full article5 min read
CoursesLessonsBrowseMy learning