Persistent data

By default, Kasm Workspaces creates containerized sessions that are ephemeral, so their contents are discarded when the session ends. Some use cases require data or configurations to persist between sessions. Kasm Workspaces provides three mechanisms for persistence, each suited to a different need.

Persistent profiles

Persistent profiles automate mounting a host directory into the Workspace as the user's home directory. They are analogous to roaming profiles on other platforms. When a profile is configured, users choose at launch whether to use the persistent profile, disable it so the session is ephemeral, or reset it to clear the contents and start fresh. Persistent profiles suit a single user who needs a consistent home directory across sessions.

Volume mappings

Volume mappings are a more general feature that maps host-level directories into the session. They can also share folders across multiple users and Workspaces, which makes them appropriate for an organizational share. You configure volume mappings at the group level or the individual Workspace level.

Cloud storage mappings

Cloud storage mappings let end users attach their own cloud storage accounts directly into the file systems of container-based sessions. Administrators configure supported storage providers, such as Google Drive, Dropbox, OneDrive, Nextcloud, and S3. Administrators then configure mappings to those providers at the user, group, or Workspace level, and end users enroll their own accounts for the configured providers from their profile.