> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corridor.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting GitHub

> Connect your GitHub account and repositories to Corridor.

To integrate Corridor with your code, the first onboarding step is connecting your version control. Currently GitHub is supported (GitHub Cloud and GitHub Enterprise via app installation).

## Prerequisites

* A Corridor account
* Admin access to the GitHub repositories you want to connect

## Connect your GitHub account

<Steps>
  <Step title="Start GitHub connection">
    In the Corridor app, click **Connect GitHub** (this appears during sign-up or on [app.corridor.dev/teams](https://app.corridor.dev/teams) under **Team Details**). This will redirect you to GitHub to authorize the Corridor GitHub App.
  </Step>

  <Step title="Select repositories">
    During the GitHub authorization flow, you'll have the option to either grant access to **All repositories** or select specific ones.

    * If you plan to use Corridor on many repos, selecting **All repositories** is convenient (you can still add only specific projects later in Corridor).
    * If you prefer to limit access, choose **Only select repositories** and pick the repos you want Corridor to have access to.

    <Note>
      If you go with selected repos, you'll need to revisit this if you want to add more projects in Corridor later (to grant Corridor access to the new repo).
    </Note>
  </Step>

  <Step title="Complete authorization">
    Approve the installation/authorization. You'll be redirected back to Corridor when done.
  </Step>
</Steps>

## Permissions requested

Corridor's GitHub App requests the following permissions needed to scan code changes and provide feedback directly on PRs:

| Permission          | Access     | Purpose                          |
| ------------------- | ---------- | -------------------------------- |
| **Code**            | Read       | Analyze code for security issues |
| **Pull requests**   | Read/Write | Post PR review comments          |
| **Checks**          | Read/Write | Update status checks             |
| **Commit statuses** | Read       | Track review status              |

<Note>
  If using GitHub Enterprise Server, ensure your admin has installed the Corridor app on your GHES instance with appropriate scopes.
</Note>

## What happens after connecting

After connecting, Corridor now has the ability to read the code and post PR comments for the repositories you allowed. However, you still need to **add each repository as a Project** inside Corridor to kick off scans (see [Adding Projects](/onboarding/adding-projects)). The GitHub connection just sets up credentials—it doesn't automatically start scanning every repo until you specify.

## Next steps

<CardGroup cols={2}>
  <Card title="Adding Projects" icon="folder-plus" href="/onboarding/adding-projects">
    Create projects from your connected repositories
  </Card>

  <Card title="PR Reviews" icon="code-pull-request" href="/features/pr-reviews">
    Learn about automated security reviews
  </Card>
</CardGroup>