Project automations
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 and is available only to its members. Whose AI credits its runs spend depends on the project's AI Credits setting – see AI credits for project automations.
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.
AI credits for project automations
A project's automations can run on the project's own AI credits or on the personal credits of the person who created each one. Project admins make the choice for the whole project in project settings, under AI Credits.
Personal – each automation spends the AI credits of its creator, the same as the tasks that person runs.
Project – every automation in the project spends the project's AI credits, and runs keep working after their author leaves the project.
Members see the setting but can't change it. The choice applies to every automation in the project, whether it was created there or assigned to it later.
Project service account
The project's AI credits belong to a service account that JetBrains Air Teams creates for the project in JetBrains Central Console, named after the project. On project credits, automation runs execute under this account instead of under the person who created or started them.
The account gets the same default AI credit limit as a regular organization user. The AI Credits section shows the project's monthly limit; to raise it, ask an organization administrator to add credits for the account. Administrators manage it in JetBrains Central Console under . For details, see Service accounts in the JetBrains Central Console documentation.
How automation runs reach the repository
The setting decides more than who pays: it decides who the run is. Repository access follows that identity.
Automation | Runs as | Reaches repositories through |
|---|---|---|
Personal | The person who created it | That person's own VCS authorization |
Project, on Personal credits | The person who created it | That person's own VCS authorization |
Project, on Project credits | The project's service account | Access granted to that account |
For GitHub repositories, this needs no setup. JetBrains Air Teams authorizes the service account for a repository when you create or edit the automation, and only for repositories you can already access yourself – so joining a project never gives anyone repository access they didn't have in GitHub. Your choice of repository doesn't change.
GitLab has no app to install, so the project needs a GitLab token of its own – see GitLab access for project automations.