Currently, workspace schedules are only a recommendation and there is no way for admins to enforce a particular shutdown behavior on workspaces. #3630, #5600.

We have seen a decent amount of feedback that warrants us supporting both "max" and "default" TTL as they serve different use cases. For example, max TTL to enforce security patches, but default TTL to ensure workspaces quickly shut down when inactive.

Let's re-introduce the "max TTL" while also keeping the "default TTL" behavior for workspaces. This will allow workspaces to have the following behavior:

• Workspaces will auto-shutdown after 2 hours of inactivity (default TTL), but cannot be alive for over 72 hours (max TTL).

Also, some admins may not want users to change the default TTL behavior of their workspaces. For example,

• All workspaces on template x will auto shut down after 2 hours of inactivity. Users cannot change this behavior.

To summarize:

• Introduce max lifetime value in template settings (while keeping default TTL): scheduling: add max lifetime  #6496
• Add a toggle in template settings to disable user-controlled shutdown behavior: scheduling: Add a toggle in template settings to disable user-controlled shutdown behavior #6497