# Project Settings

Here you configure your project's identity, access, and deployment.

For security, authentication, and policies of the running app, use [Runtime Settings](/documentation/runtime-settings.md).

### Basic Settings

You can adjust:

* **Project name (Display Name** per language**)**
* **Delete the project**

{% hint style="danger" %}
**Danger Zone: remove project**\
This action is irreversible.\
It removes project data, components, menus, and settings.

To confirm, type the **project name** and click **Confirm deletion**.
{% endhint %}

### Visual identity

Use to align the app with your brand.

Common settings:

* **Project icon**
* **Dark Mode**
* **Contrast**
* **Right to Left (RTL)**
* **Compact**
* **Layout**
  * Left menu
  * Top menu
  * Collapsed left menu
* **Font**
  * Font type
  * Font size
* **Theme colors**
  * Primary
  * Secondary
  * Info
  * Success
  * Warning
  * Error

Finish with **Save** or discard with **Cancel**.

### Languages

Here you manage the languages enabled in the project.

You can:

* See the list of configured languages.
* Add a language.
* Remove a language.

### Project team

Use to share the project with other people on the platform.

Each member can have a different role (e.g., administrator).

### GitHub

Connect a repository to synchronize code and history.

Common fields:

* **Repository URL**
* **Branch**
* **Access Token**
* **Auto-sync enabled**

Typical flow:

1. Fill in URL, branch, and token.
2. Click **Test connection**.
3. Click **Connect**.

{% hint style="warning" %}
Use a token with the smallest possible scope.\
Avoid personal tokens shared between people.
{% endhint %}

### Version history

Here you see the project's version stack.

You can:

* Identify the **current version**.
* Run a specific version.
* Revert to a previous version.

{% hint style="warning" %}
Reverting can undo UI changes and rules.\
Test in Preview before publishing to production.
{% endhint %}

### Cloud environments

A Cloud environment is where your app is published.

Examples:

* `Dev` for quick tests.
* `Staging` for acceptance testing.
* `Prod` for end users.

#### Create and publish an environment (recommended flow)

{% stepper %}
{% step %}

### Create the environment

In the environments list, click **Add**.

Fill in:

* **Environment name**
* **External domain** (optional)
* **Application server**
* **Database server**
* **File storage**

Click **Proceed to payment** or **Cancel**.
{% endstep %}

{% step %}

### Payment (Stripe)

Payment is processed securely via Stripe.

When you proceed, you will see the checkout screen.
{% endstep %}

{% step %}

### Provisioning (Not Ready → Ready)

After payment, the environment remains **Not Ready** while provisioning.

Wait about **5 minutes**.
{% endstep %}

{% step %}

### Publish

When it is ready, the status changes to **Ready**.

If you click **Publish** before that, the indicator turns red.

![](/files/be845ff0b09550b52f5733991b2905132d017b40)

When the environment is ready, it appears in green.

<figure><img src="/files/2cd668fe4eef4d08a99ecaa5635865a2c2df97be" alt=""><figcaption><p>Status ready to publish</p></figcaption></figure>

Select the environment and click **Publish**.
{% endstep %}

{% step %}

### Wait and access

After publishing, wait about **3 minutes**.

Access the app via the environment URL.

In the list, it should appear as **Ready**.

<figure><img src="/files/85aba048ebe5e6311a1a859ba0ee5e65facec8d0" alt=""><figcaption><p>Published environment</p></figcaption></figure>
{% endstep %}
{% endstepper %}

#### Edit an environment

To change settings, click the environment's gear.

{% hint style="info" %}
Environments are provisioned on AWS with IaC, containers, load balancing, auto-scaling, and high availability Multi-AZ.
{% endhint %}

### Next steps

* Fine-tuning backend and scaffold: [Editor Mode](/documentation/editor-mode.md)
* Product overview: [Platform](/documentation/platform.md)
* Connections to your stack: [Integrations](/documentation/integrations-and-api.md)


---

# 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.madrix.dev/documentation/project-settings.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.