= Defining a default persistent storage strategy in the CheCluster Custom Resource With this update, {prod-short} administrators can define a default persistent storage strategy for new workspaces by using the `CheCluster` Custom Resource: WARNING: Your users might lose workspace data if you change the storage type. * Persistent `per-user` `pvcStrategy`: + [source,yaml] ---- devEnvironments:   storage:     pvcStrategy: per-user       perUserStrategyPvcConfig:         claimSize: __<size>__         storageClass: __<classname>__ ---- + NOTE: A separate PVC is provisioned for each user's namespace and only for that user's workspaces. All of the storage for a workspace is mounted on subpaths in the PVC of the workspace. Users cannot run multiple workspaces concurrently. * Persistent `per-workspace` `pvcStrategy`: + [source,yaml] ---- devEnvironments:   storage:     pvcStrategy: per-workspace       perWorkspaceStrategyPvcConfig:         claimSize: __<size>__         storageClass: __<classname>__ ---- + NOTE: A separate PVC is provisioned for each workspace within the namespace. Users can run multiple workspaces concurrently. TIP: {prod-short} also supports `ephemeral` storage, which you can set as an attribute in the devfile. Users can override the storage strategy by entering a URL parameter when starting a new workspace. See link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.2/html-single/user_guide/index#url-parameter-for-the-workspace-storage [URL parameter for the workspace storage].