Skip to main content
Git-provider access is managed outside the Connectors catalog. In the audited workspace, Settings → Auth shows the connected provider, Settings → Code Management synchronizes repositories, and Code Review → Codebases shows repositories enabled for Code Review.

​
What is verified

Do not look for Git providers on the Connectors page. Do not infer support for an enterprise or hosted variant from another provider’s guide.

​
Manage the currently connected provider

For the provider already connected to the workspace:
  1. Open Settings → Auth and confirm the provider and connection state.
  2. Open Settings → Code Management.
  3. Select Sync to refresh the repository list, or Add Repo when that action is available.
  4. Enable one pilot repository using the controls shown for that repository.
  5. Open Code Review → Codebases and confirm that the repository appears.
  6. Run a non-draft test pull request and verify the configured read and write behavior.
For self-managed GitLab, follow the self-managed GitLab guide. For Bitbucket Cloud, follow the Bitbucket Cloud guide. Those flows can begin outside the current workspace settings UI.

​
Possible capabilities

These are capability categories, not a guaranteed permission list. Review the exact authorization screen or onboarding checklist for the provider and deployment.

​
Enterprise and self-managed requirements

Confirm with Entelligence and the provider administrator:
  • Supported provider edition and version
  • Base URL and TLS certificate trust
  • Approved network route
  • Proxy and allowlist policy
  • OAuth callback or app configuration
  • Webhook reachability and secret rotation
  • Service account or app owner
  • Private-repository policy
  • Upgrade and outage ownership

​
Verify

  • The provider connection completes through its documented onboarding path.
  • Intended repositories appear in Settings → Code Management when that page is used by the provider.
  • Enabled repositories appear under Code Review → Codebases.
  • A normal member sees only intended repositories.
  • A pilot review reads and posts only where configured.
  • Revoking the installation or credential stops future access.
  • Reconnection restores only the approved scope.

​
Next step

Run the Code Review quickstart.