Organization repository access
Setting up repository access is one part of setting up JetBrains Air Teams for an organization. For the other steps, see Set up Air Teams.
What you set up depends on the provider. GitHub needs the connection app installed for the organization that owns the repositories, and a self-hosted instance has to be registered in JetBrains Central Console first. Cloud GitLab needs nothing – each user authorizes access for themselves.
Until you register a self-hosted instance, developers don't see it in . After that, they can connect it and reach the repositories available to them. To take an instance out of JetBrains Air Teams again, select Discard connection for it on the Hosted VCS page.
GitHub
To make organization repositories available in JetBrains Air Teams, the JetBrains Air connection app must first be installed for that organization in GitHub.
This first step must be done by a user with sufficient administrative permissions in that organization – see Who can grant the app access to a repository.
Grant JetBrains Air Teams access to GitHub organization repositories
In JetBrains Air Teams, go to .
Find GitHub and click Connect.
In the GitHub flow opened by JetBrains Air Teams, install the JetBrains Air connection app for the organization.
Grant the app access either to all organization repositories or only to selected repositories.
Only the repositories granted to the app at this stage can later appear in JetBrains Air Teams.
After that, users from that organization can connect GitHub in JetBrains Air Teams and access the repositories that are available to them according to GitHub's access rules.
GitHub Enterprise Server
An administrator registers the instance in JetBrains Central Console, under . Registration creates a GitHub App on your own server and installs it into the organization that owns the repositories, so the instance gets its own connection app instead of using the JetBrains Air app from the GitHub Marketplace.
For the full flow – automatic and manual app creation, the repository permissions the app needs, and the webhook setup that JetBrains Air Teams automations rely on – see GitHub Enterprise Server in the JetBrains Air Governance documentation.
Registration and installation are one-time steps. Once the instance shows as Connected, it also appears in JetBrains Air Teams under , and every other user authorizes it for themselves – see Connect a VCS provider.
GitLab Self-Managed
An administrator registers the instance in JetBrains Central Console, under , using the credentials of an OAuth application created on your GitLab server. Unlike GitHub Enterprise Server, there's nothing to install and no repository selection to make: each developer authorizes the instance for themselves and works with the repositories they can already reach on that server.
For the full flow, see GitLab Self-Managed in the JetBrains Air Governance documentation.
Registration is a one-time step. Once the instance shows as Connected, it also appears in JetBrains Air Teams under , and every other user authorizes it for themselves – see Connect a VCS provider.