From 568c553c7b82714da687546f3c245f95b96a68e6 Mon Sep 17 00:00:00 2001 From: "sergio.corral" Date: Tue, 27 Oct 2026 12:03:23 -0300 Subject: [PATCH 1/4] [CXH-3498] docs: add when-to-use guidance, org_role capability and EMU behavior --- docs/connector.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 7d4b2a25..1056b017 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -9,7 +9,7 @@ sidebarTitle: "GitHub" **This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1 for the first time, you're in the right place. -Use this integration if your organization accesses GitHub at `github.com`. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. +Use this connector if your organization is on `github.com`. You can manage one organization per GitHub app, or several organizations with a single personal access token. It also supports fine-grained personal access tokens for authentication. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. ## Capabilities @@ -20,11 +20,16 @@ Use this integration if your organization accesses GitHub at `github.com`. If yo | Repositories | | | | Teams | | | | Orgs | | | +| Org roles | | | | GitHub Apps (NHI) | | | | Secrets - API keys | | | The GitHub connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). New accounts will send an invitation to the account owner; while an invitation is pending, the account status will be shown as **Pending**. Expired invitations also report **Pending**, distinguished by `invitation_expired` in the status details. + +**Enterprise Managed Users (EMU):** If your GitHub organization uses Enterprise Managed Users, account provisioning fails with an error stating that accounts are provisioned by your identity provider, because GitHub does not allow org invitations for managed users. To create accounts for EMU users, use your identity provider's GitHub SCIM integration. The connector still syncs and governs access for existing EMU users. + + Repository permissions that are inherited through team membership are labeled as such on the relevant entitlement's **Grants** tab in the C1 web app. [This connector can sync secrets](/product/admin/inventory) and display them on the **Inventory** page. From 7abb6c5274b9215c998631db4647cd1837c8b943 Mon Sep 17 00:00:00 2001 From: Luisina Santos Date: Wed, 4 Nov 2026 11:18:25 -0300 Subject: [PATCH 2/4] docs: link the Choose a GitHub connector guide from the top note Co-Authored-By: Claude Opus 5.5 --- docs/connector.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 1056b017..44b9279a 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -9,7 +9,7 @@ sidebarTitle: "GitHub" **This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1 for the first time, you're in the right place. -Use this connector if your organization is on `github.com`. You can manage one organization per GitHub app, or several organizations with a single personal access token. It also supports fine-grained personal access tokens for authentication. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. +Use this connector if your organization is on `github.com`. You can manage one organization per GitHub App, or several organizations with a single personal access token. It's the only GitHub connector that supports fine-grained personal access tokens. To compare the GitHub connectors and pick the right one, see [Choose a GitHub connector](/baton/choose-github-connector). ## Capabilities From 13387923bf8e0a353301a0513556e36735780424 Mon Sep 17 00:00:00 2001 From: "sergio.corral" Date: Wed, 4 Nov 2026 14:31:59 -0300 Subject: [PATCH 3/4] docs: drop unverified exclusivity claim and restore GitHub Enterprise link --- docs/connector.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 44b9279a..9d266378 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -9,7 +9,7 @@ sidebarTitle: "GitHub" **This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1 for the first time, you're in the right place. -Use this connector if your organization is on `github.com`. You can manage one organization per GitHub App, or several organizations with a single personal access token. It's the only GitHub connector that supports fine-grained personal access tokens. To compare the GitHub connectors and pick the right one, see [Choose a GitHub connector](/baton/choose-github-connector). +Use this connector if your organization is on `github.com`. You can manage one organization per GitHub App, or several organizations with a single personal access token. It also supports fine-grained personal access tokens for authentication. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. To compare the GitHub connectors and pick the right one, see [Choose a GitHub connector](/baton/choose-github-connector). ## Capabilities From ec15c7775d44c490eb134bbca5855afe36309c05 Mon Sep 17 00:00:00 2001 From: Luisina Santos Date: Wed, 4 Nov 2026 15:03:15 -0300 Subject: [PATCH 4/4] docs: state fine-grained PAT support is unique, route via the connector guide GitHub Enterprise documents only classic PAT and GitHub App auth, and GitHub Enterprise Cloud accepts only a GitHub App, so fine-grained PAT support is unique to this connector. The custom-domain pointer is replaced by the Choose a GitHub connector guide, which covers GHES and GHEC routing. Co-Authored-By: Claude Opus 5.5 --- docs/connector.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 9d266378..44b9279a 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -9,7 +9,7 @@ sidebarTitle: "GitHub" **This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1 for the first time, you're in the right place. -Use this connector if your organization is on `github.com`. You can manage one organization per GitHub App, or several organizations with a single personal access token. It also supports fine-grained personal access tokens for authentication. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. To compare the GitHub connectors and pick the right one, see [Choose a GitHub connector](/baton/choose-github-connector). +Use this connector if your organization is on `github.com`. You can manage one organization per GitHub App, or several organizations with a single personal access token. It's the only GitHub connector that supports fine-grained personal access tokens. To compare the GitHub connectors and pick the right one, see [Choose a GitHub connector](/baton/choose-github-connector). ## Capabilities