Problem

Our documentation does not clearly define user "activity" in the context of workspace scheduling. We have an "activity bump" feature that extends workspace lifetime when a user is connected to the workspace, but it's unclear what counts.

This can lead to unexpected behavior that leaves workspaces running past the expected shutdown time. An idle VSCode window, Jetbrains IDE, or browser IDE keeps workspaces alive.

Proposal

Explain what activity means, a user connected to the workspace, and what counts as being "connected." For more information on this, read an internal study conducted by engineering here. Some more nuanced technical details of this document have drifted, but the explanation of activity is correct.