Existing Resources
Is your feature request related to a problem? Please describe.
Currently, session recording in Kasm Workspaces can only be configured at the user or group level. This makes it impossible to selectively record sessions for specific workspaces without affecting all users in a group. For example, if an organization wants to record sessions only for high-risk or sensitive workspaces (e.g., a browser workspace with access to critical internal systems), they are forced to either enable recording for entire user groups — capturing far more than necessary — or forgo targeted recording altogether. This creates unnecessary data volume, raises privacy concerns for unrelated workspaces, and complicates compliance efforts.
Describe the solution you'd like
Session recording should be configurable at the workspace level, as an option directly within each workspace's settings. This would allow administrators to enable recording selectively — for example, only for a "Secure Browser" or "Dev Environment" workspace — regardless of which users or groups access it. The existing group- and user-level controls should remain in place, with workspace-level configuration acting as an additional, more granular layer of control.
Describe alternatives you've considered
- Enabling recording for all workspaces in a group: This technically achieves coverage but results in recording sessions that do not require it, raising unnecessary privacy and storage concerns.
Additional context
Workspace-level recording granularity is a common requirement in regulated industries (finance, healthcare, government) where only specific tools or environments are subject to audit or compliance obligations. Tying recording to the workspace rather than the user more accurately reflects real-world compliance boundaries. This feature would bring Kasm in line with how similar controls (e.g., clipboard restrictions, file transfer policies) are already scoped per workspace.
Existing Resources
Is your feature request related to a problem? Please describe.
Currently, session recording in Kasm Workspaces can only be configured at the user or group level. This makes it impossible to selectively record sessions for specific workspaces without affecting all users in a group. For example, if an organization wants to record sessions only for high-risk or sensitive workspaces (e.g., a browser workspace with access to critical internal systems), they are forced to either enable recording for entire user groups — capturing far more than necessary — or forgo targeted recording altogether. This creates unnecessary data volume, raises privacy concerns for unrelated workspaces, and complicates compliance efforts.
Describe the solution you'd like
Session recording should be configurable at the workspace level, as an option directly within each workspace's settings. This would allow administrators to enable recording selectively — for example, only for a "Secure Browser" or "Dev Environment" workspace — regardless of which users or groups access it. The existing group- and user-level controls should remain in place, with workspace-level configuration acting as an additional, more granular layer of control.
Describe alternatives you've considered
Additional context
Workspace-level recording granularity is a common requirement in regulated industries (finance, healthcare, government) where only specific tools or environments are subject to audit or compliance obligations. Tying recording to the workspace rather than the user more accurately reflects real-world compliance boundaries. This feature would bring Kasm in line with how similar controls (e.g., clipboard restrictions, file transfer policies) are already scoped per workspace.