> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/deploy/environments/manage-environments.md).

# Manage environments

You can add, rename, reorder and delete environments in the Hub under **Admin > Environments**. This requires the **Manage Environments** system permission. See [Create user groups](/flow-connect/working-with-connect/user-administration/user-groups/create-user-groups.md).

{% hint style="info" %}
The number of Test and Production environments available depends on your organization's subscription. When the limit for a type is reached, it is marked **Limit reached** in the **Type** list. Contact Novacura if you need additional environments.
{% endhint %}

#### **Add an environment**

1. In the Hub menu, select **Environments**.
2. Select **New Environment**.
3. Select a **Type**: *Test* or *Production*.
4. Enter a **Name** and, optionally, a **Description** (max 300 characters).
5. Select **Save**.

The new environment is added to the list of environments and becomes available as a deployment target.

{% hint style="warning" %}
The type of an environment cannot be changed after it has been created.
{% endhint %}

#### **Edit an environment**

1. In the Hub menu, select **Environments**.
2. Select the environment card, or select the three-dot menu on the card and select **Edit**.
3. Change the **Name** and/or **Description**.
4. Select **Save**.

#### **Change the order of environments**

The order decides how environments are listed on the Environments page, on the deployment screen and in the clients.

1. Open the environment you want to move.
2. Under **Position on the list**, drag the environment to its new position.
3. Select **Save**.

Test and Production environments can be placed in any order. The Development environment is always listed first.

#### **Delete an environment**

1. In the Hub menu, select **Environments**.
2. Select the three-dot menu on the environment card and select **Delete**.
3. Type the name of the environment to confirm.
4. Select **I understand the consequences of permanent deletion**.
5. Select **Delete permanently**.

{% hint style="danger" %}
Deleting an environment cannot be undone. All data, configurations and logs associated with the environment are permanently deleted, including applications and pages deployed to it, connector configuration values and system variable values. Deployed applications do not prevent an environment from being deleted.

The Development environment cannot be deleted.
{% endhint %}

#### **After adding an environment**

Before applications can be used in a new environment:

* **Configure connectors** — connector configurations are empty for a new environment. Enter the values for the new environment in each connector the applications use, or copy them from another environment on the connector's configuration page. This is done per connector. See [Managing Connectors](/flow-connect/working-with-connect/connect-to-systems/managing-connectors.md).
* **Set system variables** — system variable values are empty for a new environment. Set values where needed.
* **Deploy** — deploy the applications and pages to the new environment.

{% hint style="info" %}
End user access is granted per environment type. Users who have access to applications in Test environments automatically get access to a new Test environment, and the same applies to Production.
{% endhint %}


---

# 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.novacura.com/flow-connect/working-with-connect/deploy/environments/manage-environments.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.