Verify and manage VCS integrations.

Verify a GitHub (SaaS) integration

1. Select Settings > Data Sources & Integrations and search for GitHub Cloud.
2. Hover over and select the resulting entry.
3. Locate your instance and verify that the status is Connected.

Event subscriptions

When the integration reaches Connected, GitHub automatically provisions the event subscriptions that keep Cortex Cloud in sync with repository activity; you do not configure them. For the list of events, refer to Reference E: Subscribed GitHub events.

Identify an integration in the integrations list

Use the integrations list to identify your GitHub (SaaS) integration and review its ownership and connection status.

1. In Cortex Cloud, open Settings > Data Sources & Integrations and search for GitHub Cloud.
2. Hover over and select the resulting entry.
3. Verify that the status of your GitHub (SaaS) instance is Connected.

Review these fields to identify the integration:

• Display name. The integration appears with the GitHub organization name as its display name.
• Ownership indicator. The Ownership column identifies the ownership model: Cortex GitHub App or Customer Owned.
• Status indicator. The integration shows the standard integration status indicators: Connected, Warning, or Error.

Manage integrations

Instance-level actions

1. Navigate to Settings → Data Sources & Integrations and search for GitHub (SaaS).
2. Select the matching result.
3. Locate your instance from the displayed list, right-click it, then select an option:

   • Edit instance: Opens the onboarding wizard, where you can change the instance configuration.
   • Delete instance: Deletes the instance and previous scan data.
   • Copy entire row: Copies all row values to the clipboard.

Repository-level actions

Right-click a connected repository to Set Scanned Branches, run a manual scan through Scan Repository, modify the Scan Configuration, or Remove Repository entirely. You can toggle specific scanners and manage PR behavior in Scan Configuration.

1. Locate your instance. See Verify a GitHub (SaaS) integration above.
2. Select the instance. A list of connected repositories appears.
3. Right-click a repository, select the required action, then click Save.

Update Customer Owned GitHub App permissions or resolve integration errors

Because you own the Customer Owned GitHub App, you manage its permissions in your GitHub organization settings. If a required permission is missing or downgraded, Cortex Cloud raises a warning on the integration status that names the affected capability and includes a direct link to the GitHub App permissions page. Update the permissions in GitHub and approve them in your organization; the capability is restored without recreating the integration or re-selecting repositories. For the permissions each capability requires, see Reference C: Feature permission requirements.