# Manage environments

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/air/llms.txt).

All of your environment configurations live in `Settings | Environments`. From there you can review what you have, change a configuration, hand one over to a [project](projects.html), or delete one you no longer need.

Procedure: Browse environment configurations

1. In Air Teams, go to `Settings | Environments`.

2. The list shows every configuration you can use, whether you created it, someone shared it with you, or it belongs to a project you're a member of:

* Name – the configuration name. Click the column header to sort by it.

* Repository – the repository the configuration applies to.

* Project – the project that owns the configuration, or a dash if it's [personal](configure-environments.html#cloud_personal_and_project_environments).

* Last Used – how long ago a cloud task last ran on this configuration, or never if none has.

* Created By – who created the configuration.

3. To find a configuration in a long list, click the search icon and start typing its name.

Procedure: Edit an environment configuration

1. In `Settings | Environments`, open the configuration you want to change.

2. Change the settings you need.

3. Click Save.

Your changes apply only to newly created environments – to the new cloud tasks that use this configuration. Tasks that already exist keep the environments they started in, so they don't pick up the change, not even after you resume them.

So if a task fails because an environment variable, secret, or domain is missing, add it to the configuration and start a new cloud task.

Procedure: Update an environment configuration with an agent

Instead of editing the settings yourself, you can let an agent re-analyze the repository and update the configuration – the same [automatic
setup](create-an-environment.html#create_environment_configuration_with_agent) that can create one. Use it when the codebase has moved on and the configuration hasn't: a new dependency, a new service the tests need, or a changed build command.

1. In `Settings | Environments`, open the configuration you want to update.

2. Click the chevron next to the configuration name, then click Update Environment with Agent.

![The menu under the configuration name, open and showing Update Environment with Agent and Delete](images/environment-actions-menu.png)

3. In the Update Environment dialog, select the agent that runs the setup, then start it.

From here the run works the same way as agent-driven creation: the agent asks you for the variables and secrets it can't discover on its own, and commits any startup script changes to a separate branch rather than your default branch. See [Create
a configuration with an agent](create-an-environment.html#create_environment_configuration_with_agent).

4. Review the settings the agent changed, and adjust any of them by hand if you need to.

Procedure: Move an environment configuration to a project

If you set up a personal configuration and later want your team to own it, move it into a project. The configuration keeps its settings and history – Air Teams changes only who owns it, so tasks that are already running aren't affected.

You can move a personal configuration into a project, and a project configuration into another project. Moving a project configuration back to personal isn't supported. To move a configuration, you need to be an admin of the target project, and you need to own the configuration – be its creator if it's personal, or an admin of the project it belongs to.

1. In `Settings | Environments`, open the configuration you want to move.

2. Open the Project list and select the target project.

A personal configuration shows Personal until you pick a project. The list offers only the projects you're an admin of.

3. Click Change Project.

The button appears after you select a different project. If you edited other fields as well, save or discard those changes first – Air Teams moves the configuration as a separate action.

4. Review what the dialog reports:

* Environments used by automations – Air Teams can't move one, whether the automations are your personal ones or belong to the project the configuration is in. The dialog lists every automation that uses the configuration and links to each one, so you can check what depends on it. Click Duplicate Environment instead: the configuration stays where it is and its automations keep using it, and a copy with the same settings lands in the target project.

* Variables and secrets – environment variables and shared secrets follow the configuration. Personal secrets stay private to whoever added them, so convert them to [shared secrets](environment-variables-and-secrets.html#cloud_variables_and_secrets) if the team needs them. Variables that read their values from a [secrets provider](environment-variables-and-secrets.html#cloud_external_secrets) aren't transferred – add them again in the target project.

Then click Move Environment.

After the move, every member of the target project can use the configuration, and members of the project you moved it out of lose access – unless you shared the configuration with them directly, because explicit shares survive the move. To change who can use it, click Share – see [Share an environment configuration](share-an-environment.html#cloud_share_environment).

Procedure: Delete an environment configuration

1. In `Settings | Environments`, open the configuration you want to delete.

2. Click the chevron next to the configuration name, then click Delete.

3. Confirm the deletion.

New cloud tasks and automations can no longer use the configuration, and you can't undo the deletion. Tasks that are already running aren't affected.

If automations use the configuration, Air Teams pauses them. To resume one, select a different environment for it first.

Deleting a [project](create-a-project.html) also deletes the environment configurations that belong to it.