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

# Choose a GitHub connector

> Compare the GitHub, GitHub Enterprise, and GitHub Enterprise Cloud connectors and pick the one that fits how your GitHub environment is hosted, how you authenticate, and which capabilities you need.

To connect GitHub to C1, pick the connector that matches how your GitHub environment is hosted and which capabilities you need. C1 offers three GitHub connectors, each with its own setup and capabilities:

* **[GitHub](https://www.c1.ai/docs/baton/github.md)**: organizations on `github.com`.
* **[GitHub Enterprise](https://www.c1.ai/docs/baton/github-enterprise.md)**: GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud (GHEC), with enterprise-level features.
* **[GitHub Enterprise Cloud](https://www.c1.ai/docs/baton/github-enterprise-cloud.md)** (beta): an entire GHEC enterprise through one connector.

Use the decision guide below to pick one, then follow the setup instructions on that connector's page.

## Decision guide

Answer these questions in order to narrow down which connector to use.

**1. Where is your GitHub environment hosted?**

* **GitHub Enterprise Server (self-hosted, on your own domain):** use **[GitHub Enterprise](https://www.c1.ai/docs/baton/github-enterprise.md)**. It's the only connector that supports GHES.
* **Organizations on `github.com` that aren't part of an enterprise account:** use **[GitHub](https://www.c1.ai/docs/baton/github.md)**.
* **GitHub Enterprise Cloud:** all three connectors can work. Continue to the next step.

**2. Do you want one connector for the whole enterprise?**

The **[GitHub Enterprise Cloud](https://www.c1.ai/docs/baton/github-enterprise-cloud.md)** connector syncs every organization in the enterprise through one connector. To use it, you must be able to install one GitHub App on the enterprise and on each of its organizations. It's the only connector that syncs and provisions enterprise teams and invites users at the enterprise level.

The GitHub and GitHub Enterprise connectors work per organization instead. With a personal access token, one connector can sync several organizations. With a GitHub App, you need one connector per organization.

**3. Which capabilities do you need?**

Check the [comparison table](#compare-the-connectors) for the capabilities you need. In particular:

* **Enterprise roles, Enterprise Owner provisioning, licenses, or member last activity:** use **[GitHub Enterprise](https://www.c1.ai/docs/baton/github-enterprise.md)**.
* **Fine-grained personal access tokens:** use **[GitHub](https://www.c1.ai/docs/baton/github.md)**.
* **Personal access token authentication, organization roles, account deletion, or secrets and non-human identities:** use **[GitHub](https://www.c1.ai/docs/baton/github.md)** or **[GitHub Enterprise](https://www.c1.ai/docs/baton/github-enterprise.md)**. The GitHub Enterprise Cloud connector doesn't support these.

**4. Does your enterprise use Enterprise Managed Users (EMU)?**

All three connectors sync existing EMU users and govern their access, but none of them can create EMU accounts. See [Enterprise Managed Users](#enterprise-managed-users-emu) below.

## Compare the connectors

This table compares hosting, authentication, scope, and supported capabilities across the three connectors.

| | GitHub | GitHub Enterprise | GitHub Enterprise Cloud (beta) |
| :- | :- | :- | :- |
| **Hosting** | Organizations on `github.com` | GHES and GHEC | GHEC only |
| **Authentication** | Personal access token (classic), fine-grained personal access token, or GitHub App | Personal access token (classic) or GitHub App | GitHub App only, installed on the enterprise and on each organization |
| **Scope of one connector** | Personal access token: several organizations GitHub App: one organization | Personal access token: several organizations GitHub App: one organization | The whole enterprise |
| **Account provisioning** | Organization invitation | Organization invitation | Enterprise invitation (as an unaffiliated member) |
| **Account deletion** | | | |
| **Organization membership** | Sync and provision | Sync and provision | Sync; provisioning is limited to revoking membership and demoting owners to members |
| **Organization roles** | Sync and provision | Sync and provision | |
| **Teams** | Sync and provision | Sync and provision | Sync and provision |
| **Repositories** | Sync and provision | Sync and provision | Sync and provision |
| **Enterprise teams** | | | Sync and provision |
| **Enterprise roles** | | Sync (requires the **Enterprises** setting); Enterprise Owner provisioning with GitHub App authentication | Enterprise owners: sync only |
| **Licenses** | | Sync (personal access token only) | |
| **Member last activity** | | Sync (optional setting) | |
| **Secrets and non-human identities (GitHub Apps)** | Sync (secrets require GitHub App authentication) | Sync (secrets require GitHub App authentication) | |

### What only each connector offers

These capabilities are available on one connector and not the others:

* **GitHub:** fine-grained personal access token authentication.
* **GitHub Enterprise:** GitHub Enterprise Server support, enterprise roles and Enterprise Owner provisioning, licenses, and member last activity.
* **GitHub Enterprise Cloud:** one connector for the whole enterprise, enterprise teams, and enterprise-level invitations.

## Beta status of GitHub Enterprise Cloud

The [GitHub Enterprise Cloud](https://www.c1.ai/docs/baton/github-enterprise-cloud.md) connector is in **beta**. If you need a capability it doesn't cover yet, use the GitHub or GitHub Enterprise connector instead.

## Enterprise Managed Users (EMU)

None of the GitHub connectors can create accounts for Enterprise Managed Users. With EMU, your identity provider (IdP) creates accounts on GitHub through SCIM, and GitHub doesn't allow managed users to be invited.

* **To create EMU accounts**, set up account creation in your IdP's GitHub SCIM integration, not in a C1 connector.
* **All three connectors sync existing EMU users** and govern their access: organization, team, and repository access, plus enterprise roles or enterprise teams on the connectors that support them.
* **Account provisioning from C1 fails for EMU:**
  * **GitHub and GitHub Enterprise:** the organization invitation fails with an error saying that the organization uses Enterprise Managed Users and that accounts are provisioned by the IdP.
  * **GitHub Enterprise Cloud:** the enterprise invitation fails with an error from GitHub.
