Override custom providers at project level
Last updated: February 20, 2026
Summary
Goal: Override organization-level custom AI providers at the project level to use different API keys or endpoints per project.
Features: Project-level AI providers, custom provider configuration, provider name matching for override behavior.
Applicable To
Plans: Any
Deployments: Any
Configuration Steps
Step 1: Create organization-level custom provider
Set up your default custom provider at the organization level.
Go to Settings → Organization → AI providers
Under Custom providers, click Create
Configure your provider (e.g., name:
openai-custom, endpoint, API key)Save the provider
Step 2: Create project-level override
Create a project-level custom provider with the exact same name to override the organization-level provider.
Go to Settings → Project → Project-level AI providers
Under Custom providers, click Create
Use the exact same provider name as the org-level provider you want to override
Configure with your project-specific settings (e.g., different API key, regional endpoint)
Save the provider
Step 3: Verify override behavior
The project will now use the project-level provider instead of the organization-level provider when names match.
Project-level providers with matching names completely override org-level providers
Other org-level providers remain accessible to the project
Use this for regional API keys (US vs non-US OpenAI endpoints) or project-specific configurations
Common Use Cases
Regional endpoints: Override org-level non-US OpenAI keys with US-specific keys at project level
Project isolation: Provide project-specific API keys while maintaining org-level defaults
Custom models: Override default model endpoints for specific projects
Key Requirements
Provider names must match exactly (case-sensitive) for override to work
Project-level providers take precedence when names match
Non-matching org-level providers remain accessible to projects