Organization scope
Learn which Coder Agents settings belong to an organization, what an upgrade migrates, and who can change them.
On this page
Coder Agents configuration is split between deployment-wide settings and organization-scoped settings. Deployment-wide settings apply to every chat in the deployment. Organization-scoped settings apply only to chats that belong to that organization.
This page describes which settings belong to each scope, what an upgrade changes, and who can configure each setting.
Every deployment has at least the default organization, so the organization-scoped settings apply even when you never create a second organization. Running more than 1 organization requires a Premium license.
What each scope owns
| Setting | Scope | Where to configure |
|---|---|---|
| AI providers and credentials | Deployment | Admin settings > AI > Providers |
| Chat models | Organization | Admin settings > AI > Models |
| Default model | Organization | Admin settings > AI > Coder Agents > Organization settings |
| Admin model overrides | Organization | Admin settings > AI > Coder Agents > Organization settings |
| Personal model overrides | User, per organization | Agents > Settings > Agents |
| Personal override toggle | Deployment | Admin settings > AI > Coder Agents > Deployment settings |
| Model Context Protocol (MCP) servers | Organization | Admin settings > AI > Coder Agents > MCP servers |
| MCP server connections | User, per organization | Agents > Settings > MCP connections |
| Organization skills | Organization | Admin settings > AI > Coder Agents > Skills |
| Members can turn off organization skills | Organization | Admin settings > AI > Coder Agents > Skills |
| Your organization skill choices | User, per organization | Agents > Settings > Skills |
| Personal skills | User | Agents > Settings > Skills |
| System prompt | Deployment | Admin settings > AI > Coder Agents > Instructions |
| Organization instructions | Organization | Admin settings > AI > Coder Agents > Instructions |
| Plan mode instructions | Deployment | Admin settings > AI > Coder Agents > Instructions |
| Agent access to a template | Template | Admin settings > AI > Coder Agents > Templates |
| Advisor runtime limits | Deployment | Admin settings > AI > Coder Agents > Deployment settings |
| Computer use model | Organization | Admin settings > AI > Coder Agents > Organization settings |
| Autostop fallback and lifecycle | Deployment | Admin settings > AI > Coder Agents > Lifecycle |
| Data retention | Deployment | Admin settings > AI > Coder Agents > Lifecycle |
The Deployment settings section holds the personal override toggle and the Advisor card. The computer use model is an admin model override, so it lives in the Organization settings section.
AI providers stay deployment-wide
An AI provider holds the upstream endpoint and the credentials, so it stays a deployment-wide resource. A chat model belongs to 1 organization and references 1 provider. You select a provider when you add a model, but the dashboard never shows the provider's credentials.
Refer to Models for provider setup and model options.
Organization instructions add to the system prompt
Organization instructions add guidance for the chats in 1 organization, such as which templates, skills, or conventions to use. They never replace the deployment system prompt. When a user creates a chat, Coder adds the organization instructions after the deployment system prompt. Subagents receive the instructions of their parent chat's organization. Coder applies the instructions only when it creates a chat, so a change affects new chats and leaves existing chats unchanged. Chats in other organizations never receive them.
Refer to System prompt for the full order.
What an upgrade does
When a deployment upgrades to a release that scopes models and MCP servers to organizations, Coder moves the existing configuration:
- Every existing chat model moves to the default organization.
- Every existing MCP server moves to the default organization, with its credentials intact.
- Every moved model and MCP server stays available to the default organization's Everyone group, so current members keep access.
- The previous default model becomes the default model of the default organization.
- Coder removes the existing admin and personal model overrides.
- Coder ignores the previous Advisor model override, so you must set it again.
- The deployment-wide template allowlist becomes the per-template Allow Coder Agents to create workspaces using this template setting.
Other organizations start with no models and no MCP servers. Coder copies nothing from the default organization.
Important
Coder does not migrate the model overrides. Administrators must set the organization overrides again in the Organization settings section of Admin settings > AI > Coder Agents. Users must set their personal overrides again in Agents > Settings > Agents.
The template allowlist conversion follows these rules:
- A non-empty allowlist allows only the templates it lists, and blocks every other existing template.
- A missing or empty allowlist leaves every template allowed.
- An unreadable allowlist blocks every template, so review the template list after the upgrade.
The upgrade removes the stored allowlist, so you cannot recover the original list. Templates created after the upgrade allow agents by default.
Organizations without models or MCP servers
A new organization has no chat models and no MCP servers. Add at least 1 model before members start a chat in that organization.
When an organization has no model that the user can use, Coder does not start the chat. The user sees a message that asks an administrator to configure a chat model.
An organization with no MCP servers produces no error. Chats in that organization offer no MCP servers.
Who configures each scope
- Deployment administrators configure the providers and every setting in the Deployment settings section.
- Users with edit access to an organization's models configure that organization's models, admin model overrides, and organization instructions.
- Users with read access to an organization's models can open the Models page and the Coder Agents page, and Coder shows the fields as read-only.
- Users with access to an organization's MCP servers can open the MCP servers page.
- Users who can edit an organization's skills decide whether members of that organization can turn off organization skills for their own chats. Refer to Let members turn off organization skills for more information.
- Auditors and custom roles can hold read access without edit access.
- Users with a custom role that grants edit access without read access can save organization instructions through the API, but they can't view them.
The dashboard shows the organization picker when you can access more than 1 organization. Your access applies to the selected organization, so your controls can differ between organizations.
Manage model and MCP server access
Each chat model and each MCP server has an access list of groups and users. An entry lets a member use the model or the server. Coder adds the organization's Everyone group when you create a model or a server, so all members have access by default. You can add only the members and the groups of the organization that owns the model or the server.
To change a model's access list, open Model actions > Manage permissions on the Models page. Refer to Manage model permissions for the steps.
To change an MCP server's access list, open Server actions > Manage permissions on the MCP servers page. Refer to Access control for details.
You can also use the API:
GET /api/v2/organizations/{organization}/mcp-servers/{mcpserverconfig}/aclPATCH /api/v2/organizations/{organization}/mcp-servers/{mcpserverconfig}/acl
Let members turn off organization skills
By default, every organization skill that is turned on and that a member can use loads into that member's chats.
Users who can edit the organization's skills, such as site owners and organization admins, can let each member turn off individual organization skills, or all of them, for their own chats:
- Go to Admin settings > AI > Coder Agents > Skills.
- If you can view the skills of more than one organization, choose the organization in the organization picker.
- Turn on Members can turn off organization skills below the organization picker.
The setting is off by default and applies only to the selected organization. Coder records each change to the setting in the audit log.
Members turn off skills for their chats in Agents > Settings > Skills, as described in Turn off organization skills for your chats. Coder handles these choices as follows:
- A member's choices change only that member's chats and aren't audited.
- When an administrator turns the setting off, Coder keeps the members' choices but ignores them, so every organization skill that is turned on loads again. If the setting is turned back on, the stored choices apply again.
- When a member leaves the organization, Coder deletes that member's choices for the organization.
- When a skill is deleted, Coder deletes every choice about that skill. A new skill with the same name as a deleted one doesn't inherit anyone's choices, so members who turned off the old skill see the new one.
The setting API lives under /api/experimental/organizations/{organization}/skill-settings.
The member choice API lives under /api/experimental/organizations/{organization}/members/{user}/skill-preferences.
Both are experimental and might change.
Related pages
- Models for providers, models, and model overrides.
- MCP Servers for MCP server configuration.
- Template Optimization for the per-template agent setting.
- Organization skills for creating organization skills and sharing them with members.