> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/SaaS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/SaaS/govern/secure-your-data/projects-and-purpose-based-access-control/write-index/how-to-guides/create-and-manage-project-workspaces.md).

# Create and Manage Project Workspaces

{% hint style="warning" %}
**Deprecation notice**

Support for projects has been deprecated.
{% endhint %}

After workspaces are configured, project owners can enable workspaces within their projects. This feature allows project members to [write data](/SaaS/govern/secure-your-data/projects-and-purpose-based-access-control/write-index/how-to-guides/write-data-back.md) to the project.

## **Requirement**

You must own the project

## **Prerequisites**

* [Databricks Spark integration is configured](/SaaS/configuration/integrations/databricks/databricks-spark/how-to-guides/simplified.md).
* [Databricks workspace is configured](/SaaS/configuration/application-configuration/how-to-guides/config-builder-guide.md#add-a-workspace).
* [Databricks tables are registered in Immuta](/SaaS/configuration/integrations/data-and-integrations/registering-metadata/register-data-sources/databricks-tutorial.md).
* [External IDs have been mapped in for Databricks](/SaaS/configuration/people/users-index/how-to-guides/external-user-mapping.md).

## Create a workspace

{% hint style="info" %}
**Databricks cluster configuration**

Before creating a workspace, the cluster must send its configuration to Immuta; to do this, run a simple query on the cluster (i.e., `show tables`). Otherwise, an error message will occur when you attempt to create a workspace.
{% endhint %}

1. Navigate to the **Policies** tab and enable **Project Equalization** by clicking the Project Equalization slider to **on**.
2. Scroll to the **Workspace** section and click **Create**.
3. Select **Databricks** from the **Workspace Configuration** dropdown menu.
4. Opt to edit the sub-directory in the **Workspace Directory** field; this sub-directory auto-populates as the project name.
5. Enter the **Workspace Database Name**.
6. Click **Create** to enable the workspace.

## Delete a workspace

1. Scroll to the **Workspace** section on the policies tab and click the **toggle** to disable the workspace.
2. Click **Delete** in the workspace section.
3. Click **Delete**.


---

# 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://documentation.immuta.com/SaaS/govern/secure-your-data/projects-and-purpose-based-access-control/write-index/how-to-guides/create-and-manage-project-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.