coder · ethanndickson · Aug 7, 2026 · Jul 27, 2026 · Aug 4, 2026 · Aug 4, 2026
diff --git a/docs/ai-coder/agents/platform-controls/index.md b/docs/ai-coder/agents/platform-controls/index.md
@@ -79,14 +79,12 @@ Python backend services in the payments repo" — platform teams can guide the
 agent toward the correct infrastructure without requiring developers to
 understand template selection at all.
 
-Administrators can also restrict which templates are available to agents
-using the template allowlist at **Agents** > **Settings** >
-**Manage Agents** > **Templates**. When the allowlist is configured, the
-agent can only see and provision workspaces from the selected templates.
-When the allowlist is empty, all templates are available. This is separate
-from what developers see when manually creating workspaces, so you can apply
-stricter policies to agent-created workspaces without affecting the manual
-workspace experience.
+Administrators can also restrict which templates are available to agents at **Agents** > **Settings** > **Manage Agents** > **Templates**.
+Use the switch for each template in the list.
+The same control is available on each individual template's settings page as **Allow Coder Agents to create workspaces using this template**.
+Templates allow agents by default.
+When you disable the control, the agent cannot read the template or provision workspaces from it.
+This is separate from what developers observe when manually creating workspaces, so you can apply stricter policies to agent-created workspaces without affecting the manual workspace experience.
 
 See [Template Optimization](./template-optimization.md) for best practices on writing
 discoverable descriptions, restricting template visibility, configuring network

diff --git a/docs/ai-coder/agents/platform-controls/template-optimization.md b/docs/ai-coder/agents/platform-controls/template-optimization.md
@@ -4,38 +4,30 @@ Not every chat with Coder Agents requires a workspace. A workspace is only provi
 agent decides it needs compute — to read files, write code, run commands, or
 execute builds.
 
-When a workspace is needed, the agent reads the available templates, selects
-the appropriate one based on its name and description, and provisions a
-workspace automatically. Administrators can restrict which templates the agent
-can see using the [template allowlist](#restrict-available-templates).
+When a workspace is needed, the agent reads the available templates, selects the appropriate one based on its name and description, and provisions a workspace automatically.
+Administrators can [restrict which templates the agent can use](#restrict-available-templates).
 
 This guide covers best practices for creating templates that are discoverable
 and useful to Coder Agents.
 
 ## Restrict available templates
 
-By default, the agent can see and provision any template in the deployment.
-Administrators can restrict this to a specific set of templates using the
-template allowlist.
+By default, every template allows Coder Agents.
+Administrators can block individual templates from the template list or from each template's settings page.
 
-To configure the allowlist:
+To change which templates agents can use:
 
 1. Navigate to **Agents** > **Settings** > **Manage Agents** > **Templates**.
-2. Select the templates you want agents to be able to use.
-3. Click **Save**.
+2. Toggle the switch for each template.
 
-When the allowlist is configured, the agent's `list_templates`,
-`read_template`, and `create_workspace` tools are filtered to only include
-the selected templates. The agent cannot see or provision templates that are
-not on the list.
+The same control is available on each template's settings page as **Allow Coder Agents to create workspaces using this template**.
 
-When no templates are selected, the allowlist is inactive and all templates
-are available to agents.
+When a template does not allow agents, the agent's `list_templates`, `read_template`, and `create_workspace` tools exclude it.
+The agent cannot read the template or provision workspaces from it.
 
-The allowlist only affects agent-created workspaces. Developers can still
-manually create workspaces from any template they have access to. This lets
-platform teams apply stricter policies to agent workloads without affecting
-the manual workspace experience.
+The setting only affects agent-created workspaces.
+Developers can still manually create workspaces from any template to which they have access.
+With this setting, platform teams can apply stricter policies to agent workloads without affecting the manual workspace experience.
 
 ## Write discoverable template descriptions
 

diff --git a/docs/ai-coder/agents/tools/index.md b/docs/ai-coder/agents/tools/index.md
@@ -44,8 +44,7 @@ code), it provisions a workspace using three tools:
 | `read_template`    | Read a template's parameters and presets                  |
 | `create_workspace` | Create the workspace from a chosen template               |
 
-Administrators can restrict which templates these tools can see with the
-[template allowlist](../platform-controls/template-optimization.md#restrict-available-templates).
+Administrators can restrict which templates these tools can use with the switches on the [Templates page](../platform-controls/template-optimization.md#restrict-available-templates).
 
 ### list_templates
 
@@ -214,4 +213,4 @@ Guardrails:
   recommended.
 - The tool is idempotent: if the chat already has a workspace building or
   running, that workspace is returned instead of creating a duplicate.
-- Templates outside the administrator's allowlist are rejected.
+- Templates that do not allow Coder Agents are rejected.