For the complete documentation index, see llms.txt. This page is also available as Markdown.

Workspace settings

Enable or disable a workspace - what each does, when to use it, and how it differs from deleting.

Beyond creating and deleting, a workspace has one pause control: disable, which locks the workspace from all access without deleting it. To pause compute for cost savings, suspend individual clusters instead. This page covers enabling and disabling a workspace.

Disable a workspace

From the Control Plane:

  1. Open Workspaces in the left navigation.

  2. Find the workspace and open its row actions.

  3. Click Disable and confirm.

The status changes to Disabled. While disabled, users can't open the Compute Plane, API and driver connections are rejected, clusters are stopped, and configuration (catalogs, clusters, roles) is preserved.

Re-enable a workspace

Open Workspaces, find the disabled workspace, click Enable, and confirm. The workspace returns to Running. Clusters that were running before disable are not automatically restarted - start them manually.

Disable vs delete

Disable
Delete

Reversible

Yes (Enable)

No

Compute cost while inactive

None

None (resource gone)

Configuration preserved

Yes

No

User access

Blocked

None

Run history

Preserved

Removed

If you might bring the workspace back, disable it. Only delete when you're certain you won't.

When not to disable

Situation
Use instead

You want to pause one cluster, not the whole workspace

You want to remove a workspace permanently

See also

Last updated

Was this helpful?