Projects
A project groups the resources a team needs to work on the same codebase, so you set them up once instead of each person repeating the work:
Environments: configure a cloud environment once – the repository, VM size, environment variables, startup script, etc. – and every member runs cloud tasks with the same setup.
Automations: create automations for recurring work around the codebase, such as code reviews or bug fixing. They can reuse the project's environments and are available only to its members.
Connectors: connect an MCP server once – through an organization or service account – and every task and automation in the project uses its tools.
Secrets providers: connect the team's HashiCorp Vault once, and the project's environments read secrets from it instead of keeping copies in JetBrains Air.
Members: add your team to the project so they reuse its environments and see automation results without setting up anything themselves.
Open the Projects page in the web version of JetBrains Air, next to Tasks and Automations. Select a project in the left panel to open its page.
Create a project
Create a project
Open the web version of JetBrains Air at https://air.jetbrains.cloud.
Open the Projects page.
Click New Project.
Enter a Name and, optionally, a Description.
Under Members, add the users you want to include in the project. Learn more about project roles
Under Environments, add the environment configurations you want the project members to share. Learn more about environment configurations
Under Connectors, add the MCP server connectors the project's tasks and automations should use. Learn more about project connectors
Under Automations, add the automations you want to share with the project. Learn more about project automations
Click Save.
You become the admin of the project you create. Next, add members and create the environment configurations they will share.
Project roles
Every member of a project has one of two roles. The person who creates a project becomes its admin.
Role | What the role can do |
|---|---|
Admin | Rename the project, invite and remove members, change member roles, and create, edit, and share the project's automations and environment configurations. An admin can also delete the project. |
Member | Run cloud tasks using the project's environment configurations and use its automations. A member cannot change the project, its configurations, or its automations, but can leave the project. |
Project service account
When you create a project, JetBrains Air automatically creates a service account for it in JetBrains Central Console, named after the project.
The project's AI credits belong to this account.
Projects' automations run under its service account instead of under the user who created or started them, and consume the account's AI credits.
The service account gets the same default AI credit limit as a regular organization user.
Organization administrators can view and manage it in JetBrains Central Console under . For details, see Service accounts in the JetBrains Central Console documentation.
Manage project members
Project admins manage who belongs to the project and what each member can do.
Invite a member
On the Projects page, select the project.
Click Invite to open the Invite Members dialog.
Start typing a name or email in Search names and emails, then select the user.
In the role selector, choose Member or Admin.
Click Add.
After you click Add, the member receives an invitation email with a link to the project. JetBrains Air sends the invitation to the email address of the member's JetBrains Account, as registered in JetBrains Central Console. The member opens the link to go straight to the project in the web version of JetBrains Air.
Change a member's role
On the Projects page, select the project.
Click … in the top-right corner, then select Edit to open project settings.
In the Members section, open the role selector next to the member's name and choose Admin or Member.
Remove a member
On the Projects page, select the project.
Click … in the top-right corner, then select Edit to open project settings.
In the Members section, open the role selector next to the member's name and select Remove.
Leave a project
On the Projects page, select the project.
Click … in the top-right corner, then select Edit to open project settings.
Click Leave Project.
Add environments to a project
An environment configuration 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.
Create an environment configuration in a project
On the Projects page, select the project.
Under Environments, click New Environment.
Configure the environment as described in Create an environment configuration, then save it.
If the configuration uses personal secrets, tell project members which personal secrets to create.
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.
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.
Add automations to a project
A project can own automations that handle recurring work around its codebase – automatic code reviews, bug fixing, or flows tied to issue tracking. A project automation reuses the project's environment configurations, is available only to its members, and – for GitHub repositories – runs on the project's AI credits instead of the credits of the person who created it. See Project service account.
Create an automation in a project
On the Projects page, select the project.
Under Automations, click New Automation.
Configure the automation as described in Create an automation, then save it. The automation belongs to the project, so you don't need to set the Project field yourself.
You can also share an automation you already created within a project. Open automation settings and select the required project in the Project field. You can change the project at any time or choose None to make the automation personal again. For details, see Assign an automation to a project.
Add connectors to a project
A project can have its own connectors – managed connections to MCP servers that give the agent access to external tools. A project connector is available to every cloud task and automation in the project, so you set it up once instead of each member configuring the same MCP server. Project admins add and remove connectors; members use them without any setup.
Add a connector to a project
Open the Projects page, select the project.
Under Connectors click Add Connector.
Choose the service, click Connect, and follow the provider's authorization flow. Sign in with the shared account you want the project to use.
To remove a connector, click … next to it and select Disconnect. The project's tasks and automations then lose access to that MCP server's tools.
Add secrets providers to a project
A secrets provider is an external secrets manager that the project's environment configurations read secrets from, so a value your team already keeps in a vault doesn't have to be copied into JetBrains Air. HashiCorp Vault is the first supported provider, and a project can connect several vaults – for example, one for production and one for staging.
JetBrains Air stores the connection and its credentials, not the secrets. Each referenced secret is read from the vault when a cloud task or automation starts, and it's read from the cloud environment – so the vault has to be reachable from the internet. A vault that's only available inside your network doesn't work yet.
Project admins connect and disconnect providers. Members reference the secrets in the environment configurations they can edit.
Connect a secrets provider
Open the Projects page, select the project.
Under Secrets Providers, click Add Provider.
Under Connection, describe the vault:
Name – how the vault appears in environment configurations.
Type – the provider type. HashiCorp Vault is the only option for now.
Vault URL – the address of the vault, such as
https://vault.example.com:8200.Vault namespace – the namespace to read from, if you run Vault Enterprise. Leave it empty otherwise.
Under Authentication, provide the credentials JetBrains Air authenticates with. Vault AppRole is the only method for now, so secrets are read on behalf of the AppRole rather than of the person running the task:
AppRole path – the path where the AppRole auth endpoint is mounted,
approleby default.Role ID and Secret ID – the credentials of the AppRole. Give it read access only to the secrets the project's tasks need.
Click Save.
Now the project's environment configurations can read variables from this vault. See Read a secret from HashiCorp Vault.
Delete a project
An admin can delete a project. On the Projects page, select the project, click … in the top-right corner, and select Edit to open project settings, then click Delete.