May 26, 2025 · May 22, 2025 · May 23, 2025 · May 23, 2025 · May 23, 2025 · May 23, 2025
diff --git a/docs/admin/templates/extending-templates/prebuilt-workspaces.md b/docs/admin/templates/extending-templates/prebuilt-workspaces.md
 ## Enable prebuilt workspaces for template presets

 In your template, add a `prebuilds` block within a `coder_workspace_preset` definition to identify the number of prebuilt
 instances your Coder deployment should maintain:
 instances your Coder deployment should maintain, and optionally configure a `cache_invalidation` block to set a TTL
 (Time To Live) for unclaimed prebuilt workspaces to ensure stale resources are automatically cleaned up.

   ```hcl
   data "coder_workspace_preset" "goland" {
     }
     prebuilds {
       instances = 3  # Number of prebuilt workspaces to maintain
       cache_invalidation {
          invalidate_after_secs = 86400  # Time (in seconds) after which unclaimed prebuilds are expired (1 day)
      }
     }
   }
   ```

 After you publish a new template version, Coder will automatically provision and maintain prebuilt workspaces through an
 internal reconciliation loop (similar to Kubernetes) to ensure the defined `instances` count are running.

 The `cache_invalidation` block ensures that any prebuilt workspaces left unclaimed for more than `invalidate_after_secs`
 seconds is considered expired and automatically cleaned up.

 ## Prebuilt workspace lifecycle

 Prebuilt workspaces follow a specific lifecycle from creation through eligibility to claiming.
 However, if a Prebuilt workspace is stopped, the reconciliation loop will not destroy it.
 This gives template admins the ability to park problematic prebuilt workspaces in a stopped state for further investigation.

 ### Cache Invalidation

 Prebuilt workspaces support cache invalidation through the `invalidate_after_secs` setting inside the `cache_invalidation`
 block. This value defines the Time To Live (TTL) of a prebuilt workspace, i.e., the duration in seconds that an unclaimed
 prebuilt workspace can remain before it is considered expired and eligible for cleanup.

 Expired prebuilt workspaces are removed during the reconciliation loop to avoid stale environments and resource waste.
 New prebuilt workspaces are only created to maintain the desired count if needed.

 ### Template updates and the prebuilt workspace lifecycle

 Prebuilt workspaces are not updated after they are provisioned.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -31,7 +31,8 @@ Prebuilt workspaces are tightly integrated with [workspace presets](./parameters
		## Enable prebuilt workspaces for template presets

		In your template, add a `prebuilds` block within a `coder_workspace_preset` definition to identify the number of prebuilt
		instances your Coder deployment should maintain:
		instances your Coder deployment should maintain, and optionally configure a `cache_invalidation` block to set a TTL
		(Time To Live) for unclaimed prebuilt workspaces to ensure stale resources are automatically cleaned up.

		```hcl
		data "coder_workspace_preset" "goland" {
Expand All		@@ -43,13 +44,19 @@ instances your Coder deployment should maintain:
		}
		prebuilds {
		instances = 3 # Number of prebuilt workspaces to maintain
		cache_invalidation {
		invalidate_after_secs = 86400 # Time (in seconds) after which unclaimed prebuilds are expired (1 day)
		}
		}
		}
		```

		After you publish a new template version, Coder will automatically provision and maintain prebuilt workspaces through an
		internal reconciliation loop (similar to Kubernetes) to ensure the defined `instances` count are running.

		The `cache_invalidation` block ensures that any prebuilt workspaces left unclaimed for more than `invalidate_after_secs`
		seconds is considered expired and automatically cleaned up.

		## Prebuilt workspace lifecycle

		Prebuilt workspaces follow a specific lifecycle from creation through eligibility to claiming.
Expand DownExpand Up		@@ -95,6 +102,15 @@ Unclaimed prebuilt workspaces can be interacted with in the same way as any othe
		However, if a Prebuilt workspace is stopped, the reconciliation loop will not destroy it.
		This gives template admins the ability to park problematic prebuilt workspaces in a stopped state for further investigation.

		### Cache Invalidation

		Prebuilt workspaces support cache invalidation through the `invalidate_after_secs` setting inside the `cache_invalidation`
		block. This value defines the Time To Live (TTL) of a prebuilt workspace, i.e., the duration in seconds that an unclaimed
		prebuilt workspace can remain before it is considered expired and eligible for cleanup.

		Expired prebuilt workspaces are removed during the reconciliation loop to avoid stale environments and resource waste.
		New prebuilt workspaces are only created to maintain the desired count if needed.

		### Template updates and the prebuilt workspace lifecycle

		Prebuilt workspaces are not updated after they are provisioned.
Expand Down