Governance

Governance pages control what models and tools members may use, how they connect to source control, and how spend is observed and capped.

Models

On Models, allow or deny catalog models. Disallowed models are blocked for members. You can also set routing preference (cost / balance / quality) and require Auto models when you want the platform to pick within your allowlist.

Members see those choices in the IDE/CLI model picker — see Auto Model.

Providers

When external providers are enabled for your org, publish the org provider catalog (without secrets). Optionally allow members to add local custom providers.

MCP connections

Maintain an org MCP allowlist/catalog. Enable servers for the org, choose whether credentials are held by the org or by each user, and optionally enforce the allowlist so members cannot bypass it.

Integrations

Connect GitHub, GitLab, or Azure DevOps for Cloud Agents and project linking — without asking members for personal access tokens in Admin.

Spending & usage

Set an organization monthly spend cap and optional per-member caps. The Usage page shows period spend, requests, tokens, and breakdowns by project, user, and model.

Next

• Settings reference
• People & projects