# Managing Environments
### Definition
Environments lets you manage your campaigns across your entire development lifecycle from local development through production. This helps reduce bugs, simplify QA, and speed up delivery.
By default, your account includes:
* **1 main environment**
* **1 secondary environment**
***
### Where to find environment settings
Manage environments from:
**Settings → Feature Experimentation → Environments**\
***
### Configuration
You can **create** **additional environments** and **customize existing ones** directly within Feature Experimentation and Rollout platform.
#### Creating environments
Multiple environments allow you to mirror your engineering workflow such as staging, pre-production, production, and maintain consistent configurations across your development lifecycle.
{% hint style="warning" %}
To create a new environment, you must have a **Super Admin** role.
{% endhint %}
1. From the environment selector, click **Add environment**.
2. Enter the **name** of your new environment.
3. *(Optional)* Select a **color** for the environment. This color is used as a **visual identifier** across the platform to help you quickly distinguish environments and better organize your account.
4. Click **Create Environment**.\
You are redirected to your newly created environment.
{% hint style="success" %}
The **main environment (Prod)** always displays a **green tag.**\
This color cannot be changed, making it easy to identify production environment and avoid mistakes.
{% endhint %}
***
### Managing existing environments
You can manage your environments directly from the environment selector.
**Available actions:**
* Edit an environment name
* Edit an environment color
* Configure environment-level behaviors
* Delete an environment (with restrictions)
**Deletion rules**
You must maintain at least **two environments** at all times:
* **1 main environment** (cannot be deleted)
* **1 secondary environment**
{% hint style="danger" %}
Once an environment is deleted, it cannot be recovered.
{% endhint %}
**Environment-level configuration**
Configure the following capabilities for each environment:
* [**1 visitor, 1 experiment**](/feature-experimentation-and-rollout/sdk-and-environments/managing-environments/1-visitor-1-experiment.md)
* **Experience continuity**
* **Data export**
* **Troubleshooting mode**
***
### **For developers**
To use this environment in your application, configure its **Environment ID** and **API key** in your **codebase**.
***
#### Example workflow
> If your development lifecycle includes multiple environments such as Production, Pre-production, and Staging, you can mirror this workflow in Feature Experimentation and Rollout:
>
> 1. Go to **Settings → Feature Experimentation → Environments**
> 2. Click **Add environment**
> 3. Enter `Staging` as the environment name
> 4. Click **Create**
> 5. Go to **Settings → Teams**
> 6. Add your team members and assign the appropriate roles
>
> Once configured, you can:
>
> * Duplicate existing **campaigns** from Production or Pre-production
> * Or create new campaigns directly in the Staging environment
**Need additional information?**\
Submit your request at **.** We are always happy to help!
---
# 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.abtasty.com/feature-experimentation-and-rollout/sdk-and-environments/managing-environments.md?ask=
```
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.