beanworks-eng-shared
diff --git a/‎docs/images/templates/template-schedule-settings.png
99.9 KB b/‎docs/images/templates/template-schedule-settings.png
99.9 KB
diff --git a/‎docs/images/workspaces/quiet-hours.png
-167 KB b/‎docs/images/workspaces/quiet-hours.png
-167 KB
diff --git a/‎docs/templates/index.md
Lines changed: 4 additions & 24 deletions b/‎docs/templates/index.md
Lines changed: 4 additions & 24 deletions
diff --git a/‎docs/workspaces.md
Lines changed: 4 additions & 6 deletions b/‎docs/workspaces.md
Lines changed: 4 additions & 6 deletions
@@ -69,38 +69,18 @@ coder templates create <template-name>
 > [examples/](https://github.com/coder/coder/tree/main/examples/templates)
 > directory in the repo.
 
-## Template policies (enterprise)
+## Schedule settings (enterprise)
 
-By default, developers have unlimited workspace usage and can use any template version. Template policies allows you to:
+While workspaces can auto-stop based on activity, users set this value per-workspace it can be continuously bumped to prevent a workspace from stopping. For large enterprises, this can drive up cloud cost and introduce security concerns, as workspaces are not kept up to date.
 
-- Auto-stop workspaces after 3 hours of inactivity.
-- Require workspaces to be restarted frequently to ensure they use the most recent template version.
-- Disable workspace auto-start.
+To enforce auto-stopping, you can enforce a timeout for all workspaces, as well as a max session duration.
 
-### Stop policy
-
-Stop policies require workspaces be stopped (or restarted), regardless of activity:
-
-- Daily (Restart on next quiet hours)
-- Weekly (Restart on weekends)
-- Custom (Every 2 weeks)
-
-  ```text
-   Every [2] [Weeks] on [Friday]
-   or
-   Every [2] [Days]
-   or
-   Every [4] [Weeks] on [Saturday]
-   ```
-
-- Never
+![Workspace auto-stop settings](../images/templates/pre-filled-parameters.png)
 
 Stops occur during a user's [quiet hours](../workspaces.md#quiet-hours), which prevent interruptions. If a user is still using their workspace, they can postpone a restart up to 3 hours.
 
 Learn more about [workspace auto-stop](../workspaces.md#workspace-auto-stop)
 
-<!-- TODO: Add the dashboard screenshots. We can remove the "most recent version" bullet point once we finish template version policies -->
-
 ## Customize templates
 
 Example templates are not designed to support every use (e.g
 
@@ -37,7 +37,7 @@ information, see [Resource Persistence](./templates/resource-persistence.md).
 
 When a workspace is deleted, all of the workspace's resources are deleted.
 
-## Workspace auto-stop
+## Inactivity timeout
 
 In Coder, workspaces can auto-stop when the user is not actively using the workspace. By default, Coder recognizes the following actions as activity and will keep the workspace online:
 
@@ -47,15 +47,13 @@ In Coder, workspaces can auto-stop when the user is not actively using the works
 
 > [Custom activity](#TODO) can be registered via Coder's REST API, such as an ongoing data science pipeline.
 
-<!-- TODO. Document this. We may want to move to a custom activity section. See coder/coder[#8064](https://github.com/coder/coder/issues/8064) and coder/coder#5629 -->
-
-Your workspace's auto-stop behavior can be seen in the dashboard. Template settings in Coder determine if users can alter their workspace schedules. 
+Your workspace's auto-stop behavior can be seen in the dashboard. Template settings in Coder determine if users can alter their workspace schedules.
 
 ![TODO: use real screenshot](./images/workspaces/stops-after-3-hours.png)
 
-### Max workspace lifetime (enterprise)
+### Max session length (enterpise)
 
-Workspaces may also have a max lifetime, which enforces a stop or restart even if you are actively using your workspace.
+Workspaces may also have a max session length, which enforces a stop or restart even if you are actively using your workspace.
 
 ![TODO: use real screenshot](./images/workspaces/approaching-stop.png)