# Configuring Projects

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

<figure><img src="/files/UzShI22MRVddsP3SlxzL" alt=""><figcaption><p>Projects Menu</p></figcaption></figure>

Once a project is created, the following settings become available:

* **Name**: You can assign any name that aligns with your organization’s naming conventions.
* **Creation Date**: Displays when the project was initially created.
* **Last Contributor**: Identifies the most recent user to modify the project.
* **Project Type**: Indicates the transformation engine selected for this project.
* **Owner**: The current project owner. Ownership can be transferred if needed.

### Key Concepts

Here are the core principles that define how projects work in dex:

| Concepts    | Description                                                                                         |
| ----------- | --------------------------------------------------------------------------------------------------- |
| Consistency | Each project uses a single transformation engine to ensure a unified configuration and logic        |
| Flexibility | You can create multiple projects across different cloud providers, tailored to specific needs       |
| Isolation   | Connections are tied to individual projects and cannot be shared between them                       |
| Separation  | Projects can be organized by data usage patterns or business units for greater clarity and control. |

{% hint style="warning" %}
Connections are tied to individual projects and cannot be shared between them
{% 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-projects.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.