Skip to main content

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.

Once GitHub is connected, the next step is to import a repository as a Corridor Project. A Project in Corridor represents a repository that you want to secure.

​
Create a project

1

Open the Projects page

In the Corridor dashboard, navigate to the Projects section. Click New Project.
2

Select repository

You’ll see a list of repositories that Corridor has access to (based on the GitHub authorization you completed). Choose the repo you want to bring under Corridor’s monitoring.
3

Confirm import

Corridor will ask for confirmation to import the repository. Confirm the selection.
4

Initial scan and guardrail generation

After adding, Corridor scans the repository and generates guardrails for that project. You can add additional guardrails by selecting the project → Guardrails → Add Guardrail. See Configuring Guardrails for more info.
If you skip this step, Corridor won’t actively monitor code. Connecting GitHub alone is not enough—you must add specific repos as projects for Corridor to know where to operate.

​
Project settings

Each project has its own Settings tab. Select a project from the Projects page, then click Settings to manage the options below.

​
PR review settings

Every project inherits its PR review configuration from the team defaults set on the PR Reviews page. On a project’s Settings tab, you can override any individual setting for that project:
  • Enable Pull Request Reviews
  • Review Verbosity Mode (Strict, Balanced, Relaxed)
  • Leave Comments on Pull Requests
  • Enable Draft PR Reviews
  • GitHub Label Filter
  • Comment When No Issues Found
  • Minimum Severity to Comment On
  • Enable Threat Modeling
See PR Reviews → Configuration for what each setting does. How overrides work:
  • By default, every setting inherits from the team. Changing a setting at the team level also updates any project that hasn’t overridden that specific setting.
  • The first time you override a setting on a project, Corridor shows a confirmation dialog listing the settings that will no longer inherit from the team.
  • Overrides are per-setting. Overriding verbosity on a project does not detach the other settings from the team default.
  • Click Reset to Team Defaults to clear all overrides for the project and resume inheriting from the team.
Per-project settings are useful when repos have different noise tolerances or review needs—for example, keeping strict commenting on a customer-facing service while only reviewing (without commenting) on an internal tool.

​
Edit project name

Click Edit Project Name in the Actions section to rename the project. The Git URL and underlying repository are not affected.

​
Delete a project

Click Delete Project in the Actions section. Deleting a project removes it from Corridor and stops PR reviews, guardrails, and findings for that repository. The underlying GitHub repository is not affected.

​
Next steps

Adding Team Members

Invite your team to Corridor

Dashboard

Track security metrics