# Manage Air in IDEs on user machines > For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/air/llms.txt). Organizations typically configure AI access and workspace policies in [JetBrains Console](ai-settings.html) or [JetBrains IDE Services](https://www.jetbrains.com/ide-services/). As an organization administrator, you can also control Air in IDEs on individual machines with the machine-wide `jcp.json` configuration file. Use `jcp.json` to turn off Air in IDEs on a machine or make a specific organization the only JetBrains AI [authorization source](air-in-ides-authorization.html) in Air in IDEs. The file is a JSON object with two optional fields: * `allowAir`: set it to `false` to turn off Air in IDEs on the machine. If it is `true` or omitted, the file does not turn off Air in IDEs. * `organizationId`: set it to your organization ID to restrict JetBrains AI authorization to that organization and enforce the policies of its organization workspaces. These settings are machine-local. They do not change your organization's configuration or affect other machines. > **Note:** > These controls apply only to Air in IDEs. They do not control agents or tools installed and run independently, such as agents launched directly from a terminal. ## Deploy the configuration file To deploy the file to multiple machines, use your company's device-management tools, such as Microsoft Intune, Jamf, or Microsoft Configuration Manager (SCCM). Apply device restrictions so that only an administrator or the root user can modify or delete the file. A local administrator can still modify or remove the file, so use your device-management tools to prevent this. In [Remote Development](https://www.jetbrains.com/remote-development/), deploy the file to the machine where the Air in IDEs process runs. The policy is read by each process on its own machine. Place the file in the machine-wide location for the operating system: | Operating system | Location | | --- | --- | | Windows | `%ProgramFiles%\JetBrains\Air\jcp.json` | | macOS | `/Library/Application Support/JetBrains/Air/jcp.json` | | Linux | `/etc/xdg/JetBrains/Air/jcp.json` | Air in IDEs ignores copies of the file in other locations, including user folders. > **Note:** > Air in IDEs reads `jcp.json` once per process. A change takes effect only after you restart the IDE. ## Turn off Air in IDEs on a machine The `allowAir` setting turns off Air in IDEs on the machine where the file is deployed. It works in all IDE builds, including EAP builds, IDEs that run without a license, and IDEs activated with a personal license. Procedure: 1. Create a `jcp.json` file with the following content: ```JSON { "allowAir": false } ``` You do not need to specify `organizationId` to turn off Air in IDEs. 2. Place the file in the [machine-wide location](#jcp-json-location) for your operating system. 3. Restart the IDE. When Air in IDEs is turned off: * Air in IDEs is unavailable and does not load organization settings. * The agent catalog is unavailable. * Air in IDEs entry points and features are hidden, including the New Session button, Agent Sessions tool window, [global prompt](air-in-ides-start-a-session.html#start-global-prompt) (`Ctrl` pressed twice), notes in diffs, commit message generation, and other Air in IDEs features. To turn Air in IDEs on again, delete the file or set `allowAir` to `true`, and then restart the IDE. If you keep the file, make sure that it contains a valid configuration. If the file is invalid, Air in IDEs is turned off for the IDE. Unknown fields are ignored. > **Note:** > Agents and tools launched independently outside Air in IDEs, such as terminal agents, are not controlled by `allowAir`. [Custom ACP > agents](air-in-ides-manage-agents.html#custom-acp-agent) that users describe in a local `acp.json` file also remain available. ## Enforce organization policies By default, your organization's workspace policies apply when a user selects one of the organization's [workspaces](air-in-ides-authorization.html#jetbrains-ai-organization) in the IDE. Without `organizationId`, users can use other AI authorization options available to them. To make your organization's JetBrains AI access and workspace policies mandatory, specify your organization ID in `jcp.json`. When the file contains `organizationId`: * JetBrains AI authorization in Air in IDEs is limited to the specified organization. * Air in IDEs offers only eligible workspaces from that organization. If one eligible workspace is available, Air in IDEs selects it automatically. The user cannot select a workspace from another organization or clear the selection. * If the user is not a member of the organization or does not have an AI seat there, JetBrains AI is unavailable. Air in IDEs identifies the required organization and suggests signing in with another account or contacting the organization administrator. * Until the required organization workspace is selected, Air in IDEs blocks JetBrains AI access and does not fall back to free or personal access. * Personal JetBrains AI subscriptions, [Junie Lite](air-in-ides-authorization.html#junie-lite), and AI from other organizations are unavailable. * If Air in IDEs cannot retrieve the required organization access or provisioning information, it retries the connection and does not switch to free or personal access. > **Note:** > The `organizationId` setting restricts JetBrains AI authorization to the specified organization. It does not define the organization's policies, override regional availability, or override policies configured in IDE Services. Procedure: Find your organization ID 1. Open [JetBrains Console](https://console.jetbrains.cloud/) in a browser. 2. Copy the organization UUID from the URL in the address bar: ```TEXT console.jetbrains.cloud/org/ ``` Do not use the customer code, the ID of an organization workspace, or the organization name. Procedure: Configure the organization ID 1. Create a `jcp.json` file with the ID of your organization: ```JSON { "organizationId": "" } ``` 2. Place the file in the [machine-wide location](#jcp-json-location) for your operating system. 3. Restart the IDE. 4. In the IDE, sign in with an account that has AI access in the organization. Confirm that personal subscriptions and other JetBrains AI authorization options are unavailable. > **Warning:** > If the file is invalid, Air in IDEs is turned off for the IDE. The IDE log identifies the file and the error.