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

# Git providers

> Manage the Git provider connected to the workspace and use deployment-specific onboarding for self-managed GitLab or Bitbucket Cloud.

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

| Provider path            | Verification                                                                                                      |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| GitHub.com               | Verified in the audited workspace under **Settings → Auth**, **Code Management**, and **Code Review → Codebases** |
| Self-managed GitLab      | Documented through a dedicated, deployment-specific onboarding flow; it is not a general Connector                |
| Bitbucket Cloud          | Documented through a dedicated service-account and API-token onboarding flow; it is not a general Connector       |
| GitLab.com               | Not verified in the audited workspace; confirm availability and onboarding with Entelligence                      |
| GitHub Enterprise Server | Not verified in the audited workspace; confirm supported version and deployment requirements                      |
| Bitbucket Data Center    | Not verified in the audited workspace; confirm supported version and deployment requirements                      |

<Warning>
  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.
</Warning>

## 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](/gitlab-selfhosting). For Bitbucket Cloud, follow the [Bitbucket Cloud guide](/bitbucket-cloud). Those flows can begin outside the current workspace settings UI.

## Possible capabilities

| Capability         | Why it may be needed                                 |
| ------------------ | ---------------------------------------------------- |
| Repository content | Analyze code and generate documentation              |
| Pull requests      | Read changes and post reviews                        |
| Comments or issues | Reply, summarize, or run supported bot conversations |
| Checks/status      | Report review status where supported                 |
| Metadata           | Map repositories, organizations, and identities      |
| Webhooks/events    | Detect pull-request or repository changes            |

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](/code-review/setup).