# Manage Workspaces A workspace is owned by an organization, and members of the organization can create, scale, and terminate workspaces. ## Create a Workspace To create a workspace, in the left navigation pane, select **Create New > Workspace**. Follow the provided instructions. A workspace cannot be renamed. Note that the workspace `admin` password is configured when the workspace is first created. SingleStore recommends that you save this password as you will need it to log into the database outside of the Cloud Portal, such as when using a SQL client. This is also referred to as the “Master Username” in the Cloud Portal, which is `admin` by default. ## Opt-in to Preview Features & Updates When enabling this option, the deployment receives the latest features and updates as soon as they are available. The configuration is suitable only for non-production deployments and cannot be changed after creation. Perform the following steps to get access to the Preview Features. 1. In the [Cloud Portal](http://portal.singlestore.com), select **Create New > Workspace**. 2. Under **Advanced Settings**, enable **Opt-in to Preview Features & Updates**. ## View Database Storage Usage and Cost To view a database’s storage usage and cost: * Navigate to the organization name in the left navigation pane: **(ORG:) > Billing & Usage > Usage Estimate > Storage Usage** to view storage used. * Navigate to the organization name at the top **(ORG:) > Billing & Usage > Usage Estimate > Billable > Storage Billed On-Demand (Average Monthly GB)** to view the monthly storage cost. * Note that the storage cost is billed in US dollars (`$`) and the storage price is dependent on the [deployment region](https://www.singlestore.com/managed-service-pricing/) that was selected when the database was created. ## Resize a Workspace Workspace size can be modified by simply selecting another size in the Cloud Portal. To resize a workspace,navigate to **Workspaces**, select the three dots under the **Actions** column, and select **Resize & Scale** from the list. Resizing operations may require provisioning new instances from the cloud provider, and delays in availability can affect the overall completion time. Active workloads can further increase scaling duration. SingleStore recommends completing or minimizing active workloads before initiating resize operations. When reducing the size, ensure the new size can accommodate the existing workload. For example, when scaling down from S-4 to S-1, utilization must be below 25% to ensure a smooth scale-down process. Estimated times are not guaranteed and may vary depending on cloud provider provisioning and workspace workload. ## Suspend and Resume a Workspace Workspaces do not need to be running when there is no active workload querying a database. To save cost, workspaces can be suspended when inactive.  Databases will be retained as long as the Workspace Group containing the database exists. > **📝 Note**: Backup operations in SingleStore Helios fail if a workspace is in the process of resuming, suspending, or terminating. Starting a backup during these state transitions interrupts the operation and returns the following error:``` > ERROR 1317 ER_QUERY_INTERRUPTED: Leaf Error: Query execution was interrupted > ``` ## Suspend a Workspace To suspend the workspace, navigate to **Workspaces**, select the three dots under the **Actions** column, and select **Suspend**. Users and Firewall rules will be retained. While suspending a workspace, the system does not forcefully terminate or block active workloads. To avoid delays, SingleStore recommends stopping or pausing all workloads before initiating the suspend operation. If workloads remain active, the suspended operation may take significantly longer to complete. ## Resume a Workspace To resume a suspended workspace, navigate to **Workspaces** and select **Resume** under the **Actions** column for the workspace. Resume operations may take a few minutes to attach databases and come online. Resume operations may take a few minutes to attach databases and come online. Resume times can vary as cloud providers provision instances at different speeds. These provisioning delays occur within the cloud provider’s infrastructure layer and are not deterministically controlled by SingleStore. Therefore, consistent resume times are not guaranteed. ## Auto Suspend a Workspace Auto suspend allows you to configure a workspace to automatically suspend either after a set period of time or after a period of inactivity. It can be configured on an existing workspace, or set at the time of creation. There are two types of auto suspend:** Idle** and **Scheduled**. Only one type can be enabled at a time. * **Idle:** the workspace will get suspended after X seconds of engine inactivity. The time only takes effect from the point when the settings are enabled. For example, if you set it for 30 minutes but the workspace already has an engine idle time of one hour before the settings are enabled, then the workspace will get suspended only after 30 minutes from the time the settings are enabled. * **Scheduled:** the workspace will get suspended after X seconds have passed, irrespective of its activity. (*Note*: this type of auto-suspend is not available for Trial users.) The task that auto-suspends the workspaces runs every 5 minutes, so there can be a maximum difference of five minutes between the time when the workspace should be suspended and when it will actually get suspended. Once a workspace is resumed, you can either keep the previous auto-suspend settings or disable them. The default behavior keeps the previous settings. The default auto-suspend settings at the time of workspace creation are: * For trial users, the settings are enabled by default to 20 minutes of idle time. * For standard users, the settings are disabled by default. > **📝 Note**: When a workspace resumes from auto-suspend, SingleStore Helios requests new compute capacity from the cloud provider. Capacity availability depends on the provider and may not be immediate, which can delay workspace resume operations. ## Terminate a Workspace To terminate a running workspace, navigate to **Workspaces**, select the three dots under the **Actions** column, and select **Terminate** from the list. ## Data Retention in SingleStore Helios Service Post Termination Encrypted data from terminated deployments is automatically and securely purged from all systems on termination, and any administrative backup data is purged within 14 days. Hence, it is not possible to recover data from a terminated deployment. If you need to retain data post-termination, SingleStore recommends that you back up your data to an external object storage bucket. ## Cloud Workload Identity and Delegated Entities Cloud Workload Identity represents a set of Kubernetes and AWS resources and configurations that are provisioned for each workspace. It enables workspace workloads, such as pipelines, to use IAM Roles for Service Accounts (IRSA) to access cloud resources without long‑lived static credentials. Workloads can use this identity to authenticate to cloud provider services without storing or rotating static credentials. Refer to [Cloud Workload Identity and Delegated Entities](https://docs.singlestore.com/cloud/user-and-workspace-administration/cloud-workload-identity-and-delegated-entities.md) for more information. *** Modified at: May 12, 2026 Source: [/cloud/user-and-workspace-administration/manage-organizations/manage-workspaces/](https://docs.singlestore.com/cloud/user-and-workspace-administration/manage-organizations/manage-workspaces/) (An index of the documentation is available at /llms.txt)