Workspace model availability

Model availability depends on the product surface and authentication boundary. A ChatGPT workspace model setting isn’t a universal model switch for Codex in the ChatGPT desktop app, Codex CLI, IDE extension, Codex cloud, or Platform API.

For the complete administration model, see Roles and workspace permissions.

Identify the model boundary

Check the current source for the surface the user is actually using. Don’t copy a model catalog or assume that a ChatGPT model-picker setting has the same effect for Codex in the ChatGPT desktop app, Codex CLI, IDE extension, Codex cloud, and the API Platform.

Separate access from runtime permissions

Model access determines whether a model is available to the authenticated user on a supported surface. Local permission profiles and managed requirements determine what an agent can do after a local run starts, such as which files it can change or which network destinations it can reach.

A permission profile can’t grant model access. Model access also can’t weaken the sandbox, approval policy, network controls, or source-system permissions that apply to a run.

Troubleshoot model access

If a user can’t select an expected model:

• Confirm the product surface and sign-in method.
• Confirm the ChatGPT workspace or Platform API organization and project.
• Review the current access controls for that authentication boundary.
• Check whether the selected local client or Codex cloud supports the model.

Current sources

• ChatGPT Enterprise and Edu models and limits
• Manage workspace settings
• Role-based access control
• Codex models
• Codex feature availability by plan
• Authentication

Related docs

• Admin rollout guide
• Groups and provisioning
• Roles and workspace permissions
• Managed configuration