# Configuring Workspaces

{% hint style="info" %}
To **create, edit, or delete** Workspaces, go to the **side menu → Organization → Settings**.
{% endhint %}

###

### Overview

Workspaces belong to environments and are typically used by individual users. A workspace is your personal space to develop models, test logic, and run pipelines. Once your changes are validated, you can commit them to the environment branch, promoting them to the broader project.

dex automatically creates a default workspace whenever a new environment is created. However, you can create additional workspaces for sandboxing, team collaboration, or parallel feature development.

### Workspace Settings

When creating a workspace, you’ll be prompted to enter the following:

* **Name:** Provide a clear and descriptive name to help identify the workspace.
* **Description (Optional):** Optionally, include a brief description to clarify the purpose or scope of the workspace.

Once these fields are filled in, click **Create workspace** to complete the setup.

Changes made within a workspace are isolated until explicitly committed to the environment branch. This allows for safe iteration and experimentation without affecting others.

### Naming Conventions and Examples

Using a consistent naming convention helps teams stay organized, especially when multiple users or teams are working in parallel. Here are a few suggestions:

| Use Case                 | Suggested Naming Pattern              |
| ------------------------ | ------------------------------------- |
| Individual developer     | `gus-dev`, `ana-ws`, `maria-test`     |
| Feature-specific work    | `discount-logic`, `campaign-metrics`  |
| Temporary testing        | `test-import-schema`, `debug-filters` |
| Cross-team collaboration | `marketing-v1`, `finance-exploration` |

For example, if you're exploring a new revenue attribution model, you might create a workspace called `revenue-attribution-pilot`. If a data engineer named Jack is working on a new connector, they might name their workspace `jack-connector-dev`.

{% hint style="info" %}
Tip: Use hyphens instead of spaces and keep names short but informative.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.dexlabs.io/lakehouse-platform/about-dex/workflow-management/configuring-workspaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.