coder · johnstcn · Apr 24, 2023 · Apr 4, 2023
diff --git a/admin/organizations/manage.md b/admin/organizations/manage.md
@@ -13,17 +13,32 @@ Provide a **name** and (optionally) a **description** for this organization. If
 you want this to become a **Default organization**, make sure to check the box
 for this.
 
+You can control the
+[auto-start behaviour](../../workspaces/lifecycle.md#auto-start) for workspaces
+in this organization. You can configure:
+
+- **Autostart Days of Week**: configures on which days of the week workspaces in
+  the organization may automatically start. If you do not want workspaces to
+  auto-start in the organization _at all_, you can simply deselect all weekdays
+  here.
+- **Workspace Shutdown Behavior**: The number of hours a workspace may be idle
+  before Coder stops it automatically to help free up resources.
+- **User-controlled workspace shutdown behavior**: Whether end-users can set the
+  desired workspace shutdown behavior. If disabled, Coder uses the
+  organization's default setting.
+
 You can also control how Coder manages resources for workspaces in this
 organization. You can set the:
 
 - **CPU Provisioning Rate**: sets the ratio of virtual CPUs to physical CPUs; if
   you set a higher ratio, you can schedule a larger number of workspaces per
   node, though it will also lead to greater CPU contention.
-- **Workspace Shutdown Behavior**: The number of hours a workspace may be idle
-  before Coder stops it automatically to help free up resources.
-- **User-controlled workspace shutdown behavior**: Whether end-users can set the
-  desired workspace shutdown behavior. If disabled, Coder uses the
-  organization's default setting.
+- **Memory Provisioning Rate**: sets the ratio of requested versus maximum RAM
+  allocated to workspaces. If you set a higher ratio, you can schedule a larger
+  number of workspaces per node, though it will lead to greater memory
+  contention. See
+  [memory overprovisioning](../workspace-management/memory-overprovisioning.md)
+  for more information.
 
 Finally, you can set **Resource Quotas**. These are limits on the number of
 **CPUs** and **GPUs**, as well as the amount of **memory** and **disk space**

diff --git a/admin/workspace-management/index.md b/admin/workspace-management/index.md
@@ -17,6 +17,9 @@ Administrative users can modify a variety of workspace-related behaviors.
 - You can modify the [workspace shutdown behavior](shutdown.md) on a
   per-organization basis to optimize resource usage.
 
+- You can configure the autostart days of week on a per-organization basis to
+  minimize unnecessary resource consumption.
+
 - You can [install multiple IDEs](installing-jetbrains.md) onto your image so
   that users have alternatives to the default option (VS Code).
 

diff --git a/admin/workspace-management/memory-overprovisioning.md b/admin/workspace-management/memory-overprovisioning.md
@@ -4,6 +4,10 @@ Coder allows you to set memory provisioning ratios for each of your
 organizations. By changing this ratio, you can change the number of workspaces
 that fit onto a single Kubernetes node.
 
+> **Note:** This may cause the Linux Kernel to terminate user workloads if there
+> is insufficient system memory available. You can read more about this topic
+> [here](https://www.kernel.org/doc/gorman/html/understand/understand016.html).
+
 ## Step 1: Enabling memory provisioning
 
 A site admin/manager must complete these steps:

diff --git a/assets/admin/create-an-org.png b/assets/admin/create-an-org.png
diff --git a/assets/admin/edit-an-org.png b/assets/admin/edit-an-org.png
diff --git a/assets/workspaces/autostart_save_preferences.png b/assets/workspaces/autostart_save_preferences.png
diff --git a/assets/workspaces/enable-autostart.png b/assets/workspaces/enable-autostart.png
diff --git a/assets/workspaces/set_autostart_time.png b/assets/workspaces/set_autostart_time.png
diff --git a/assets/workspaces/set_autostart_timezone.png b/assets/workspaces/set_autostart_timezone.png
diff --git a/workspaces/autostart.md b/workspaces/autostart.md
@@ -15,6 +15,7 @@ Your workspace must be:
   days)
 - Off (auto-start doesn't work when workspaces are _on_ to prevent the
   triggering of a rebuild while you're working)
+- The current day of week must be allowed for auto-start by your organization.
 
 Coder may trigger auto-start up to 5 minutes before your scheduled time to
 ensure all queued workspaces are ready on time.
@@ -28,6 +29,12 @@ ensure all queued workspaces are ready on time.
 
    ![Set auto-start time](../assets/workspaces/set_autostart_time.png)
 
+   You can also set your local timezone. This ensures that your workspace will
+   start at the correct time if you experience seasonal Daylight Savings Time
+   (DST) changes.
+
+   ![Set auto-start timezone](../assets/workspaces/set_autostart_timezone.png)
+
 1. Select the workspaces for which you want to enable auto-start and save.
 
    ![Select workspaces to auto-start](../assets/workspaces/autostart_save_preferences.png)

diff --git a/workspaces/lifecycle.md b/workspaces/lifecycle.md
@@ -30,6 +30,12 @@ Users can configure a workspace
 which sets the time when Coder will rebuild and start their workspaces. Users
 typically set this time to coincide with the start of their working day.
 
+Organizations can also configure the days of week on which workspaces are
+permitted to start automatically. For example, if users tend to not start their
+workspaces on Saturday or Sunday, organization managers can exclude these days
+by
+[editing the organization](../admin/organizations/manage.md#editing-an-organization).
+
 ## Auto-off
 
 Organizations can set an

diff --git a/workspaces/preferences.md b/workspaces/preferences.md
@@ -71,5 +71,9 @@ the Coder CLI:
 
 ## Auto-start
 
-Auto-start allows you to set the time when Coder automatically starts and builds
-your workspaces. See [auto-start](autostart.md) for more information.
+Auto-start allows you to set:
+
+- The time when Coder automatically starts and builds your workspaces.
+- Your preferred timezone.
+
+See [auto-start](autostart.md) for more information.