- Published on
GitHub Enterprise Slack: Cloud vs Server Setup
- Authors

- Name
- Maruan
GitHub Enterprise Cloud and GitHub Enterprise Server connect to Slack through different routes. Cloud installs the GitHub app from the Slack Marketplace, while Server cannot use that app and needs a private Slack app that you generate from the management console. Pick the wrong route and nothing you do afterwards will work.
This guide covers the native GitHub integration for Slack on both deployments, how to check which one you are on, how to install and subscribe a repository, how to test with a pull request that changes nothing in your codebase, and what to check when notifications do not arrive. Every setup step below follows GitHub's own documentation, and the Server steps are scoped to version 3.20 because the documented steps are version-specific.
GitHub Enterprise Slack: Cloud and Server use different install routes
Enterprise Cloud uses the GitHub app from the Slack Marketplace. Enterprise Server does not. GitHub's GHES 3.20 documentation states that the GitHub app in the Slack Marketplace cannot be used with GitHub Enterprise Server. Instead, a site administrator builds a private Slack app from the management console.
The decision in one place:
Enterprise Cloud: Slack admin adds the GitHub app, then people run
/github subscribe OWNER/REPOin a channel.Enterprise Server 3.20: GHES administrator enables Chat integration in the management console, generates a private Slack app with a Slack configuration token, then installs it.
The two routes also differ in who does the work. On Cloud, anyone with permission to install apps in the Slack workspace can start. On Server, you need access to the appliance's management console, which usually means your platform team, not a repository owner.
One more split worth knowing early: installing the app is one task, and subscribing a repository to a channel is another. Most "it is installed but silent" reports come from skipping the second.
First confirm your deployment and version (hostname alone can mislead)
Do not guess your deployment from the URL. A github.com address suggests Cloud, but Enterprise Cloud organizations can sit behind custom domains. A company-branded hostname does not prove you are on Server, and a custom hostname does not prove you are on Cloud either.
Ask your GitHub administrator two questions and get the answers in writing:
Are we on GitHub Enterprise Cloud or GitHub Enterprise Server?
If Server, which version is the appliance running?
The version matters because GitHub publishes the Slack instructions per Enterprise Server release. The steps in this guide match the 3.20 documentation. If your appliance runs a different version, open the documentation for that version and follow it instead of assuming the 3.20 steps apply. The same rule covers firewall and network requirements: do not rely on a blanket claim about ports or connection modes unless the docs for your exact version state it.
Wrong docs version is a common cause of failed setups. Someone follows the Cloud page on a Server appliance, looks for a Marketplace app that cannot work, and loses an afternoon.
Enterprise Cloud: install the GitHub app and subscribe a repository
On Enterprise Cloud, install the GitHub app into the Slack workspace once, invite it to a channel, then subscribe a repository. GitHub's documentation says the integration needs installing only once per workspace, by anyone with admin permissions in that Slack workspace.
The sequence:
In Slack, add the GitHub app with Add to Slack. You need permission to install apps in that workspace.
Authorize the connection to your GitHub account when prompted.
In the channel that should receive updates, run
/invite @githubso the app can post there.Subscribe a repository with the command below.
/github subscribe OWNER/REPOSubscription is per channel and per repository. Having the app in the workspace does not send anything anywhere on its own. If a teammate asks why a channel is quiet, check whether that channel has a subscription before checking anything else.
You are not stuck with a flat stream of posts. For quiet-channel setups, see our guides on GitHub Slack branch filters and label filters.
Enterprise Server 3.20: build the private Slack app from the management console
On Enterprise Server 3.20, you create a private Slack app from the management console rather than installing anything from the Marketplace. The steps below follow the 3.20 documentation.
Open the management console at
YOUR-GHES-INSTANCE:8443and go to Chat integration.Enable GitHub Chat integration and choose Slack.
In Slack, open Slack API Applications and generate a workspace app configuration token.
Paste that token into the App configuration token field in the management console.
Select Generate App, then Save settings.
Install the generated app by visiting
<instancename>/_slack/orslack.<instancename>.
Treat the configuration token as a secret. Do not paste it into tickets, chat, screenshots or shared runbooks, and keep it out of logs. When you document this setup internally, write a placeholder such as <APP_CONFIGURATION_TOKEN> and store the real value in your secrets manager.
A community walkthrough covers the same native route in a shorter form, and it works as a second read. For exact fields and menu names, the official page for your version wins.
If you are comparing options, know what this route is: GitHub's own integration, built per instance. It gives rich notifications like those on Cloud, but you own the private app.
Slack Enterprise Grid: org-wide install is not repository subscription
On Slack Enterprise Grid, installing the GitHub integration across workspaces is a separate step from subscribing repositories. GitHub's Cloud documentation says an admin or owner of a Slack Enterprise Grid organization can install the integration across multiple workspaces in the organization.
That org-level install makes the app available. It does not choose which repositories post to which channels. After it, each team still needs the app invited to its channel and a subscription for each repository it wants:
/github subscribe OWNER/REPOA common pattern on Grid: an org owner installs once, announces it, and then every team assumes alerts will start flowing. Nothing posts until someone subscribes. Put the subscribe command in your team onboarding checklist.
Also keep two things apart that sound alike: notification subscriptions in Slack, and any Copilot repository defaults you may have configured. They are unrelated settings.
Test with a non-destructive pull request: pass and fail outcomes
Test by opening a pull request that changes nothing of value, then watching the subscribed channel. Create a short-lived branch, add a harmless edit such as a line in a scratch file or a whitespace change to a README, and open a pull request against a repository you subscribed. Do not merge it. Close it when you finish and delete the branch.
What a pass looks like:
A message for the new pull request appears in the channel you subscribed.
Closing the pull request produces a matching update in the channel.
What a fail looks like, and where to go next:
Nothing appears at all: check the subscription exists for that exact channel and repository, then the app invitation.
It appears for a public repository but not a private one: see the permissions section below.
It never appears on Server: recheck the install step and that you followed the docs for your version.
Do not read a delay as proof of anything. Put no promised delivery time in your runbook, and re-check the channel after a reasonable wait before changing settings. A test PR shows whether the route works end to end, and that is all it needs to do.
Troubleshooting by symptom (private repos, missing channel invite, wrong docs version)
Match what you see to the cause, starting with the cheapest check.
Private repository posts nothing. Public repositories work, a private one is silent. Check both the subscriber’s repository permissions and the installed app’s repository access. Our guide to fixing GitHub Slack private repo notifications walks through the permission checks so this post does not need to repeat them.
App installed, subscription command does nothing. The app is probably not in the channel. Run /invite @github in that channel, then subscribe again.
Channel quiet after a successful subscribe. Confirm you subscribed the right OWNER/REPO. Verify the exact organization and repository name against the intended repository; an incorrect name can fail or select a different existing repository.
Review comments or reminders missing. These are separate behaviors from the first post. See review comments not showing and reminders not sending.
Instructions do not match your screen. You are likely reading the wrong docs version. Cloud steps will not match a Server appliance, and Server steps differ between releases. Open the page for your deployment and version.
On Server, no install page loads. Recheck that the app was generated and settings saved in the management console before visiting the install address.
FAQ: Does Slack integrate with GitHub, and what differs on Enterprise?
Yes. GitHub publishes a native integration for Slack that posts repository activity into channels and lets people subscribe with /github subscribe OWNER/REPO. On Enterprise, the difference is the route. Cloud uses the Marketplace app, and Server 3.20 uses a private Slack app you generate yourself.
If your repositories are on GitHub.com, GitLab.com or self-hosted GitLab and you want one updating Slack card per pull request or merge request, MergeMe does that. It is a separate product from GitHub's native integration. Its verified host list does not establish GitHub Enterprise Server compatibility. For Enterprise Server, follow the native private-app steps above.
Pick the right route first, then prove it with a throwaway pull request
A failed GitHub Enterprise Slack setup can result from following installation instructions for the wrong deployment. Confirm your deployment and version with your administrator, follow the matching official page, subscribe a repository, and run a test pull request that you close without merging. If your teams also work in repositories on GitHub.com, GitLab.com or self-hosted GitLab and want one updating card per PR or MR in Slack, you can try MergeMe free on the Hobby plan, with one channel mapping and five user mappings.
FAQs
Does Slack integrate with GitHub on Enterprise Cloud?
Yes. On Enterprise Cloud you install the GitHub app from the Slack Marketplace, invite it to a channel with /invite @github, and subscribe a repository with /github subscribe OWNER/REPO. GitHub's documentation says the app needs installing only once per workspace, by someone with Slack admin permissions.
Can I use the Slack Marketplace GitHub app with GitHub Enterprise Server?
No. GitHub's Enterprise Server 3.20 documentation states the Marketplace app cannot be used with Enterprise Server. Administrators instead enable Chat integration in the management console and generate a private Slack app using a Slack workspace app configuration token, then install it from the instance's Slack address.
How do I integrate GitHub with Slack Enterprise Grid?
An admin or owner of the Slack Enterprise Grid organization can install the GitHub integration across multiple workspaces. That makes the app available but does not subscribe any repositories. Each channel still needs the app invited and a /github subscribe OWNER/REPO run for every repository it should follow.
Does MergeMe support GitHub Enterprise Server?
MergeMe’s verified supported hosts are GitHub.com, GitLab.com and self-hosted GitLab. GitHub Enterprise Server compatibility is unconfirmed. For the native GitHub integration on Enterprise Server, follow the private Slack app instructions for your appliance version.