> 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.md).

# Workspaces

A workspace is an isolated environment for a team or project - its own catalogs, clusters, access control, and run history.

A **workspace** is an isolated environment within e6data. Each workspace has its own:

* Catalogs (metastores you've connected)
* Clusters (compute that runs queries)
* Access control (users, roles, and service accounts)
* Run history

Workspaces are the unit of isolation in e6data. You typically have one workspace per environment (for example, `prod`, `staging`) or per team.

## Workspace types

When you create a workspace, you pick a deployment model:

| Type            | What it means                                                          |
| --------------- | ---------------------------------------------------------------------- |
| **Serverless**  | e6data manages the compute environment. Your data stays in your cloud. |
| **In Your VPC** | Compute runs inside your own Kubernetes cluster.                       |

See [Deployment models](/query-engine/get-started/deployment-models.md) for the differences.

## In this section

* [Create and manage workspaces](/query-engine/guides/workspaces/create-and-manage-workspaces.md) - set up and update a workspace
* [Workspace settings](/query-engine/guides/workspaces/workspace-settings.md) - enable or disable a workspace
* [Delete workspace](/query-engine/guides/workspaces/delete-workspace.md) - permanently remove a workspace

## Choosing how many workspaces to create

Common patterns:

| Pattern                 | Workspaces                                    |
| ----------------------- | --------------------------------------------- |
| Environment isolation   | One per environment: `prod`, `staging`, `dev` |
| Team isolation          | One per team or product line                  |
| Tenant isolation (SaaS) | One per customer tenant                       |

There's no hard limit on workspace count. Each is independently billed for compute, and access control is per-workspace.

## Workspace lifecycle

```
[Provisioning] → [Running] → [Deleted]
                     ↓
                 [Disabled]
                     ↓
                 [Running]
```

* **Provisioning** - initial setup
* **Running** - normal operation
* **Disabled** - administrative pause; resume with Enable
* **Deleted** - permanently removed; not recoverable

## Disable vs delete

| Action      | Purpose              | Reversible   | Compute cost         |
| ----------- | -------------------- | ------------ | -------------------- |
| **Disable** | Administrative pause | Yes - enable | None                 |
| **Delete**  | Permanent removal    | No           | None (resource gone) |

Disable for compliance holds or offboarding when you might bring the workspace back; delete only when you're certain you won't. To pause compute for cost savings, suspend individual clusters instead.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.