- Published on
Reconnect GitHub to Slack: Switch Accounts Safely
- Authors

- Name
- Maruan
To reconnect GitHub to Slack with a different account, run /github signout in Slack, then /github signin, and authorize with the GitHub account you actually want linked. You do not need to reinstall the app or rebuild anything first.
The confusion usually comes from one word doing three jobs. "Connected" can mean your personal account is linked to your Slack user, the app is installed in the workspace, or a channel is subscribed to a repository. Only the first one is broken when you linked your personal account instead of your work account. This guide covers that fix for the official GitHub app on GitHub.com and leaves the other two alone.
Short answer: sign out, then sign in with the right account
Open any Slack channel or direct message where the GitHub app is available, type /github signout, and send it. That disconnects the GitHub account currently linked to your Slack user. Then type /github signin and follow the prompt to authorize again.
The whole fix is those two commands plus one careful decision in the browser: which GitHub identity you are signed in as when the authorization page loads. Most wrong-account links happen because the browser was already logged into a personal profile and someone clicked the authorize button without looking.
Don't start by uninstalling the app or removing channel subscriptions. Neither touches the thing that is actually wrong, and both create cleanup work you didn't need.
Three different connections: personal account, app installation, channel subscriptions
The personal account link is per Slack user. It answers one question: which GitHub identity does this person act as when they use /github? Your teammate can be linked to their work account while you are still linked to a personal one. Signing out affects your link, not theirs.
The app installation is per workspace. Someone installed the GitHub integration for Slack, and the repositories or organizations it can see are governed by what was authorized during that install. The integration's own README lists the permission scopes requested on the GitHub and Slack side. Switching your personal account does not reinstall this.
Channel subscriptions are per channel. A command like /github subscribe owner/repo tells the app to post that repository's activity into that channel. It is a separate setting from who you are signed in as. If you only want a channel to stop receiving a repository's alerts, that is a different job, covered in GitHub Slack unsubscribe: stop alerts for one repository.
Here is the mental diagram:
Slack user -> linked GitHub account (fix this with signout and signin) Slack workspace -> installed GitHub app and repository authorization (leave alone) Slack channel -> subscribed repositories (leave alone)
The official docs don't spell out what happens to subscriptions when you sign out, so don't assume either way. Treat the three layers as independent, check your channel afterward, and re-subscribe only if something is actually missing.
Step by step: switch the GitHub account linked to your Slack user
Work through these in order.
In Slack, open a channel or DM where the GitHub app is present. If you can't find it, the docs say slash commands work in any channel or direct message where the app is available. A channel without the app needs the app invited first, for example with /invite @github.
Type /github signout and send it. This is the documented command that disconnects your GitHub account from your Slack user.
Type /github signin and send it. This restarts the sign-in workflow.
Follow the link or button Slack gives you. It opens GitHub in your browser.
Before you approve anything, read which GitHub account the page shows (next section).
Approve the authorization, return to Slack, and confirm the link worked.
Never paste a password, token or one-time code into Slack at any point. The flow runs through GitHub's own authorization page, so if anything asks you to type a secret into a Slack message, stop.
Pick the right identity in the browser and check authorization
The browser decides which account you link, not Slack. If your browser session is already signed in to your personal GitHub profile, the authorization page will happily attach that one.
Before approving, check the avatar and username in the top right of the GitHub page. If it's the wrong account, switch to the right one first. A private window, or a browser profile you keep for work, removes the guesswork because it starts with no GitHub session.
Then read what you are authorizing. The integration documents the GitHub and Slack permission scopes it asks for and why. If your work repositories live in an organization, check whether that organization needs to approve the app or grant access. A correctly linked account still can't see a repository the organization hasn't authorized, and that looks like a failed link when it's really an access rule.
If you want a repository-access angle specifically, that is a different problem from switching identities. Treat it separately instead of re-linking over and over.
Validate with a permitted repository, and what stays separate
Test with a repository you know your intended account can read. Pick something ordinary, not the most sensitive repo you have. Validate in your direct message with the GitHub app or a restricted channel whose members may all see that repository. Do not post private repository links into a broader channel. The app can unfurl GitHub links into previews, and a correct preview for a repository only your work account can see is a quick sign the link is right. If previews fail, see GitHub Slack link previews not showing: checks and fixes.
Also confirm the change is personal. Your teammates are unaffected, because the link belongs to your Slack user. Their identity, their subscriptions and the workspace install did not change.
What stays separate after a successful switch:
The workspace install and its repository authorization.
Channel subscriptions, which you check by looking at what the channel still posts, not by assuming.
Filters and notification settings attached to those subscriptions.
If a channel stops posting a repository after you re-link, subscribe again with /github subscribe owner/repo and then review your filters. The README documents branch and label filters, which you can read about in GitHub Slack branch filters: fix commit notifications.
When the problem is not your account link
Signout and signin only fix one layer. If the symptom is something else, change layers.
The app doesn't answer in a channel. The app is probably not in that channel. Invite it and try again.
Your account is linked correctly but a repository is invisible. This is an organization or repository authorization issue, not an identity issue. Ask an organization owner to check the app's access.
Alerts are missing for a repository. Check the channel's subscription and its filters before touching your account.
You are on GitHub Enterprise Server or an enterprise setup. The integration README distinguishes GitHub.com (including cloud-hosted Enterprise), data residency on ghe.com and GHES, and they involve different installs. See GitHub Enterprise Slack: cloud vs server setup.
A teammate's link is wrong, not yours. Only they can fix it, by running the same two commands in their own Slack account.
Work the smallest layer first. Your personal link is the cheapest to change and the easiest to undo.
FAQ on reconnecting GitHub to Slack
The short answers are in the FAQ below. The core of it fits in one line: /github signout, then /github signin, and check the browser identity before you approve.
Optional: one updating card per PR or MR with MergeMe
Once your account is linked correctly, the official app covers a lot, including threaded notifications, parent message updates and scheduled pull request review reminders, all described in its docs. If you want to reshape your team's pull request flow in Slack, MergeMe is a separate option. It shows each GitHub pull request or GitLab merge request in Slack as one card that updates in place. It works with GitHub.com, GitLab.com and self-hosted GitLab in one workspace, and its Hobby plan is free. It doesn't replace or repair the native app's authentication, so fix your account link first.
Fix the link, leave the install alone, then decide on your card flow
A wrong GitHub account in Slack is a one-user problem with a two-command fix: /github signout, then /github signin with the identity you checked in the browser. Leave the workspace install and channel subscriptions untouched unless they are what is actually failing.
FAQs
How do I reconnect GitHub to Slack with a different account?
In Slack, run /github signout to disconnect the GitHub account linked to your Slack user, then run /github signin to restart sign-in. In the browser, check which GitHub account is active before you approve, and switch it if needed. You do not need to reinstall the app.
Does /github signout remove the GitHub app from my Slack workspace?
No. The official docs describe it as disconnecting your GitHub account from your Slack user. The workspace install and repository authorization are separate layers. Check your channels afterward for subscriptions, and re-subscribe with /github subscribe only if something stopped posting.
Why did Slack link my personal GitHub account instead of my work account?
The browser session decides which account gets linked. If you were already signed in to a personal GitHub profile when the authorization page opened, that is what was attached. Sign out, use a private window or work browser profile, and check the avatar before approving.
Do I need to reinstall the GitHub Slack app to switch accounts?
No. Switching accounts changes your personal link, not the workspace installation. Reinstalling also will not fix a wrong identity. Run /github signout and /github signin first. Look at the app's repository or organization authorization only if a repository stays invisible afterward.
Does MergeMe fix GitHub Slack authentication problems?
No. MergeMe does not repair the official app's account link; use /github signout and /github signin for that. MergeMe is an option for how pull requests appear in Slack: one updating card per GitHub pull request or GitLab merge request, with a free Hobby plan.