> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/workspaces/workspace-settings.md).

# 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](/query-engine/guides/workspaces/delete-workspace.md) when you're certain you won't.

### When not to disable

| Situation                                              | Use instead                                                                       |
| ------------------------------------------------------ | --------------------------------------------------------------------------------- |
| You want to pause one cluster, not the whole workspace | [Cluster suspend and resume](/query-engine/guides/clusters/suspend-and-resume.md) |
| You want to remove a workspace permanently             | [Delete workspace](/query-engine/guides/workspaces/delete-workspace.md)           |

## See also

* [Create and manage workspaces](/query-engine/guides/workspaces/create-and-manage-workspaces.md)
* [Delete workspace](/query-engine/guides/workspaces/delete-workspace.md)
* [Cluster suspend and resume](/query-engine/guides/clusters/suspend-and-resume.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/workspaces/workspace-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.