# Project environments

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

An [environment configuration](configure-environments.html) captures what a codebase needs to build and run – the VM size, internet access, and the variables and secrets tasks rely on. Set it up once at the project level, and every member runs cloud tasks against the same environment. Project admins create and edit these configurations; members run tasks against them but can't change them.

If the configuration you need already exists as a personal one, or belongs to another project, you can [move it into this project](manage-environments.html#move_environment_procedure) instead of setting it up again.

Procedure: Create an environment configuration in a project

1. On the Projects page, select the project.

2. Under Environments, click New Environment.

3. Set up the environment as described in [Create an environment configuration](create-an-environment.html#create_environment_configuration).

4. If the configuration uses personal secrets, tell project members which personal secrets to create.

> **Note:**
> Known temporary limitation: Air Teams does not yet prompt members for the personal secrets that a configuration requires. Until this prompt is available, each member must create their own personal secrets before they run tasks. Shared secrets and plain environment variables are available to all members automatically. See [Add environment variables and secrets](environment-variables-and-secrets.html#cloud_variables_and_secrets).

## Share a project's environment

An environment configuration you create from the project page belongs to the project and is automatically shared with everyone in it. You are its Owner, and every other project member gets Can view access to run cloud tasks with the configuration.

![The Share Environment dialog for a project environment](images/environments-list.png)

If needed, click Share to share the configuration with people outside the project – other users, service accounts, or user groups – or to change a project member's access to Can edit or Can view.

For details, see [Share an environment configuration](share-an-environment.html#cloud_share_environment).