Manage indexing settings
On the Air Context page, an admin can block or allow all Air Context indexing for the organization, or block only on-demand indexing through the Air Context CLI. Blocking all indexing also blocks on-demand indexing.
On-demand indexing lets repositories be indexed by running the Air Context CLI manually or in CI pipelines. Developers and service accounts require AI access to run on-demand indexing through the Air Context CLI.
Blocking indexing stops future indexing but does not delete anything. The existing indexes remain available to AI agents until you delete them.
Block all Air Context indexing for your organization
To stop all indexing in the organization, block Context indexing. After that, no repository in the organization is indexed anymore, neither by JetBrains Central nor on demand.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the Settings pane, in the Context indexing row, click Block.
A confirmation dialog is displayed.
In the Block indexing in the organization dialog, click Block indexing.
All indexing is blocked, and a confirmation message is displayed below the Settings pane.
Block on-demand indexing
By default, on-demand indexing is allowed, which means repositories can be indexed by running the Air Context CLI. These repositories appear on the On-demand indexing tab.
To prevent repositories from being indexed by running the Air Context CLI, manually or in CI, an admin can block on-demand indexing. Blocking on-demand indexing has the following effects:
Future indexing through the Air Context CLI is rejected, even for repositories hosted on the organization's GitHub account.
Existing indexes of on-demand repositories remain available until you delete them.
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the Settings pane, in the On-demand indexing row, click Block.
A confirmation dialog is displayed.
Confirm that you want to block on-demand indexing.
On-demand indexing is blocked, and a confirmation message is displayed below the Settings pane.
The repositories indexed on demand stay on the On-demand indexing tab.
Delete indexes after blocking
When indexing is blocked, the message below the Settings pane includes an option to delete all remaining indexes at once. To delete the indexes of specific repositories only, select them in the list of repositories and click Delete indexes in the toolbar that appears, as described in Manage indexing for multiple repositories.
In the message about blocked indexing, click Delete indexes.
A confirmation dialog is displayed.
Confirm the deletion.
Deleting the indexes may take some time. Until it is done, the affected repositories show the Deleting status.
Allow indexing again
Air Context indexing is allowed by default. If an admin blocks all indexing or only on-demand indexing, either one can be allowed again at any time.
Allow on-demand indexing
In the sidebar, under Integrations, select Air Context.
If you don't see this page, your role doesn't have the necessary permissions.
In the Settings pane, in the On-demand indexing row, click Allow.
The Allow on-demand indexing dialog reminds you that repositories are indexed on demand by running the Air Context CLI manually or in CI on your organization's infrastructure.
Click Allow indexing.
On-demand indexing is allowed again.
To allow all Air Context indexing, click Allow in the Context indexing row and confirm.
If the on-demand indexes were deleted while on-demand indexing was blocked, they are not restored as soon as you allow it again. An index appears on the On-demand indexing tab only when the Air Context CLI is run on the repository again.