Jun 19, 2025 · Jun 19, 2025 · Jun 19, 2025
diff --git a/docs/admin/templates/managing-templates/schedule.md b/docs/admin/templates/managing-templates/schedule.md
 lifetime feature. Templates can choose to use a max lifetime or an autostop
 requirement during the deprecation period, but only one can be used at a time.

 ### Priority and interaction with user settings

 When both template-level autostop requirements and user-configurable autostop are enabled:

 - **Autostop requirement always takes precedence** - This sets the maximum deadline that cannot be extended by user settings
 - **User autostop settings act as minimums** - Users can set shorter autostop durations but cannot exceed the requirement
 - **The earliest deadline wins** - The system will use whichever shutdown time comes first

 #### Example scenarios

 **Scenario 1**: Template requires daily stops, user sets 7-day autostop

 - **Result**: Workspace stops daily during quiet hours (requirement takes precedence)

 **Scenario 2**: Template requires weekly stops, user sets 2-day autostop

 - **Result**: Workspace stops after 2 days of inactivity (user setting is shorter)

 **Scenario 3**: Template requires daily stops, user disables autostop

 - **Result**: Workspace still stops daily during quiet hours (requirement cannot be overridden)

 ## User quiet hours

 > [!NOTE]
diff --git a/docs/user-guides/workspace-scheduling.md b/docs/user-guides/workspace-scheduling.md
 before checking connections again (1 hour by default). Template admins can
 modify this duration with the **activity bump** template setting.

 > [!NOTE]
 > If your template administrator has configured an "Autostop Requirement", your workspace may shut down more frequently than your configured autostop duration. The autostop requirement ensures compliance and template updates by enforcing mandatory shutdowns during your quiet hours, regardless of your personal autostop settings.

 ![Autostop UI](../images/workspaces/autostop.png)

 ## Activity detection

 Licensed admins may also configure failure cleanup, which will automatically
 delete workspaces that remain in a `failed` state for too long.

 ## Frequently Asked Questions

 **Q: Why did my workspace shut down even though I set a 7-day autostop?**

 A: Your template likely has an autostop requirement (daily, weekly, etc.) that takes precedence over user settings. Autostop requirements are enforced by template administrators to ensure compliance and apply template updates. Check with your administrator about the template's scheduling policies.

 **Q: Can I prevent the autostop requirement from shutting down my workspace?**

 A: No, autostop requirements cannot be overridden by users as they are enforced for compliance and updates. However, you can configure your quiet hours to ensure shutdowns happen at convenient times for you in your timezone.

 **Q: When exactly will my workspace shut down if there's an autostop requirement?**

 A: Workspaces with autostop requirements will shut down at the start of your configured quiet hours on the days specified by the template (e.g., daily, weekly). This ensures shutdowns don't happen during your working hours.

 **Q: What happens if I set a shorter autostop duration than the template requirement?**

 A: Your workspace will shut down based on whichever deadline comes first. For example, if the template requires weekly stops but you set a 2-day autostop, your workspace will stop after 2 days of inactivity.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -93,6 +93,28 @@ Autostop requirement is disabled when the template is using the deprecated max
		lifetime feature. Templates can choose to use a max lifetime or an autostop
		requirement during the deprecation period, but only one can be used at a time.

		### Priority and interaction with user settings

		When both template-level autostop requirements and user-configurable autostop are enabled:

		- Autostop requirement always takes precedence - This sets the maximum deadline that cannot be extended by user settings
		- User autostop settings act as minimums - Users can set shorter autostop durations but cannot exceed the requirement
		- The earliest deadline wins - The system will use whichever shutdown time comes first

		#### Example scenarios

		Scenario 1: Template requires daily stops, user sets 7-day autostop

		- Result: Workspace stops daily during quiet hours (requirement takes precedence)

		Scenario 2: Template requires weekly stops, user sets 2-day autostop

		- Result: Workspace stops after 2 days of inactivity (user setting is shorter)

		Scenario 3: Template requires daily stops, user disables autostop

		- Result: Workspace still stops daily during quiet hours (requirement cannot be overridden)

		## User quiet hours

		> [!NOTE]
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -39,6 +39,9 @@ workspace if you're still using it. It will wait for the user to become inactive
		before checking connections again (1 hour by default). Template admins can
		modify this duration with the activity bump template setting.

		> [!NOTE]
		> If your template administrator has configured an "Autostop Requirement", your workspace may shut down more frequently than your configured autostop duration. The autostop requirement ensures compliance and template updates by enforcing mandatory shutdowns during your quiet hours, regardless of your personal autostop settings.

		![Autostop UI](../images/workspaces/autostop.png)

		## Activity detection
Expand DownExpand Up		@@ -140,3 +143,21 @@ determines how long workspaces will remain in the dormant state before automatic

		Licensed admins may also configure failure cleanup, which will automatically
		delete workspaces that remain in a `failed` state for too long.

		## Frequently Asked Questions

		Q: Why did my workspace shut down even though I set a 7-day autostop?

		A: Your template likely has an autostop requirement (daily, weekly, etc.) that takes precedence over user settings. Autostop requirements are enforced by template administrators to ensure compliance and apply template updates. Check with your administrator about the template's scheduling policies.

		Q: Can I prevent the autostop requirement from shutting down my workspace?

		A: No, autostop requirements cannot be overridden by users as they are enforced for compliance and updates. However, you can configure your quiet hours to ensure shutdowns happen at convenient times for you in your timezone.

		Q: When exactly will my workspace shut down if there's an autostop requirement?

		A: Workspaces with autostop requirements will shut down at the start of your configured quiet hours on the days specified by the template (e.g., daily, weekly). This ensures shutdowns don't happen during your working hours.

		Q: What happens if I set a shorter autostop duration than the template requirement?

		A: Your workspace will shut down based on whichever deadline comes first. For example, if the template requires weekly stops but you set a 2-day autostop, your workspace will stop after 2 days of inactivity.