Introduction
The Integrations page is the home of the Discovery phase. It is where you manage integrations and run Discovery to find the projects and repositories across your organization. Open it from the Integrations section in the left navigation.
Discovery works in two phases. First, Discovery scans an integration to find its projects and repositories. Then Detection scans those repositories to find AI. Running Discovery from this page is what populates the Detect AI tables, where you review the results and run Detection.
Discovery can run by hand or on a schedule. A VCS integration can be scheduled to scan every week or every month. Each scheduled run discovers repositories, runs Detection and creates or rescans a Bill of Materials (BOM) for each repository that contains AI. Scheduling is described in the Scheduling Recurring Scans for a VCS Integration article.
The page consolidates integration management under a tabbed layout with two tabs. The VCS tab manages version control system integrations and is documented below. The Cloud Sensor tab manages CloudSensor integrations and is documented in the CloudSensor Overview article.
VCS Tab
This tab lists your VCS integrations, shows their discovery, connection and schedule status, and launches Discovery. The tab opens with a count of integrations, an Add New VCS Integration button, a search-by-name field, a Filters control, and a Customize Table control.
Columns
- Name
- Description
- VCS Service
- Discovery Status reflects the discovery phase for the integration. Values are Unscanned, Pending, Queued, In Progress, Completed, Partially Failed, Failed, Skipped, and Aborted.
- Validation Status reflects the connection to the VCS, shown as Valid or Invalid with a timestamp. An integration typically becomes Invalid when its personal access token expires.
- SSH Key
- Last Scheduled Scan shows when the most recent scheduled run took place. Discovery that you run by hand is not included.
- Next Scheduled Scan shows when the next scheduled run will take place.
- Actions holds the primary button. It starts as Discover Repos, which runs Discovery to find the integration's projects and repositories and populate the Detect AI table. When Discovery finishes as Completed or Partially Failed, the button becomes Detect AI, which opens the Detect AI page filtered to that integration. When Discovery finishes as Failed, the button stays Discover Repos so you can run Discovery again. To run Discovery again from any status, use Re-run Discovery in the row flyout.
Scan times show in your local time. Both scheduled scan columns show by default.
How Discovery Status Is Set
Discovery Status reflects the results of the projects in the integration's most recent Discovery scan.
- Completed means every project in the scan succeeded.
- Partially Failed means some projects failed and the rest succeeded. It shows in amber.
- Failed means every project in the scan failed.
A project that never ran counts as failed. To see which projects failed, open the Detect AI page for the integration.
Scans that ran before release 2026.11.1 keep the status they recorded. Running Discovery again updates the integration's status.
Filters
- VCS Service - Azure DevOps, Bitbucket, Bitbucket Data Center, GitHub, GitHub Enterprise Cloud, GitHub Enterprise Server, GitLab, GitLab Self-Managed
- Discovery Status - Unscanned, Pending, Queued, In Progress, Completed, Partially Failed, Failed, Skipped, and Aborted
- Validation Status - Valid or Invalid
Customize Table
Customize Table lets you drag to reorder columns and show or hide them using the eye icon. Actions is locked visible.
Row Flyout
Clicking a row opens a flyout titled with the integration name.
- Discovery Status: The discovery phase for the integration.
- Findings: The count of Projects and the count of Repos.
- Integration Type: The VCS service and authentication method.
- Scan Schedule: Shows Scheduled with the Frequency (Weekly or Monthly), Next scan and Last scan, or shows Not scheduled when the integration has no active schedule.
Flyout actions are:
- Go To Detect AI
- Re-run Discovery runs Discovery again and updates the integration's Discovery Status.
- Schedule Scans sets up a weekly or monthly scan schedule.
- Edit Scheduled Scans changes the frequency of an existing schedule.
- Stop Scheduled Scans stops future scheduled runs.
- Edit Integration
- Get Webhook Details
- Enable SSH
- Validate Integration
- Delete Integration
Scheduling, editing and stopping scans needs the VCS Scan Schedules Update permission. Scheduling scans or changing the frequency also needs the Detect AI scan permission and Bill of Materials Create. Without them, the scheduling buttons are disabled. For timing, the schedule limit and what each run creates, see the Scheduling Recurring Scans for a VCS Integration article.





