A desktop app shows a user-permission menu assigning secure access to selected files.
GitHub Desktop has stopped making you sign out of one account to use another. It now lets you sign in with more than one account on the same host, including GitHub.com, GitHub Enterprise Server, and GHE.com. The change shipped in GitHub Desktop 3.7.0 and was announced on November 19, 2026. Anyone who has juggled a personal login and a work login on Windows will know the old routine. It meant sign out, sign in, and a browser that "helpfully" picked the wrong session.

A desktop app shows a user-permission menu assigning secure access to selected files. What changed​

Until now, Desktop was effectively a one-account-per-host tool. Third-party guides captured the old limit: one GitHub.com account plus one GitHub Enterprise Server account at the same time. People worked around it with SSH host aliases, tokens embedded in remote URLs, or separate Desktop profiles. A community feature request on the Desktop repository, tracked as issue #3707, had accumulated years of discussion. GitHub itself calls this one of the most requested features in the Desktop community. That is GitHub's own characterization, and no request count is given.

According to the changelog, with this release you can:

  • Add more than one account for a single host, with no fixed limit.
  • Associate each repository with a specific account, so clone, publish, and Git operations use the right credentials automatically.
  • Choose an account when adding or cloning a repository that multiple signed-in accounts can access, or let Desktop infer it when only one can.
  • Change a repository's account association at any time from repository settings or the repository list's context menu.

Existing setups should survive the upgrade. Existing repositories are migrated automatically to the account you were already using, so if you only have one account per host, nothing changes for you.

Adding a second account on Windows​

GitHub's documentation lays out the steps. First update to 3.7.0, then:

  1. Open the File menu and click Options.
  2. On the Accounts pane, click Add GitHub.com account. For GitHub Enterprise Server or GHE.com, click Add GitHub Enterprise account instead.
  3. Follow the sign-in prompts.

On macOS the path is GitHub Desktop > Settings > Accounts. The docs add a practical tip: your browser might ask which GitHub account to use even if you're already signed in. Pick the account you want to add, or sign in to a different one, or you may end up re-adding the account you already have. The Accounts pane lists GitHub.com accounts under "GitHub.com". Enterprise Server and GHE.com accounts appear under "GitHub Enterprise", grouped by hostname.

How Desktop picks an account for each repository​

Each repository can be assigned to one account on its host. Per the docs, Desktop uses that account for clone, publish, and Git operations. More precisely, it uses it for GitHub API requests and for HTTPS authentication on push, pull, and fetch. The assignment happens when you clone, add, or publish:

  • Clone window, "GitHub" tab: an Account dropdown appears at the top, but only if you're signed in to more than one account. The repository list reflects what that account can access.
  • Clone window, "URL" tab, or Add Local Repository: Desktop checks which of your accounts on that host can reach the repository. If one can, it's assigned automatically. If several can, you're asked to choose. Public repositories are accessible to every account, so with multiple accounts on a host you will always be asked.
  • No account has access: the repository is added without an assignment. A private-repo clone over HTTPS fails in that case.
  • Publish Repository window: you choose from an Account dropdown. If the repository's assigned account is signed in, it's preselected.

Changing or removing an assignment​

There are two routes, both documented by GitHub:

  • Repository settings: choose Repository > Repository settings, open the Remote pane, pick from the Account dropdown, and click Save. Choose None (unassigned) to remove the association.
  • Repository list: click Current Repository, right-click the repo, select Account, and pick an account. A checkmark marks the current one. A signed-out account shows as "@username (Signed out)".

You can only pick accounts signed in to the repository's host.

What happens when Desktop needs credentials and has no assignment​

If a repository has no assigned account, Desktop opens a "Repository account" window when it needs one. Examples include HTTPS push or pull credentials, refreshing pull requests, and creating a fork. Background fetches never open this window. If you aren't signed in to any account on that host, Desktop asks you to sign in instead.

If the assigned account has been signed out, the prompt asks you to sign in again. If you have another account on that host, you can click Choose another account to reassign the repository.

Signing out without losing your mapping​

When you sign out of an account that has repositories assigned to it, Desktop asks whether to keep those assignments. Leave Clear repository account assignments deselected and signing back in restores the old mapping. Select it, and Desktop asks you to choose an account the next time it needs credentials. The docs also state that if a token becomes invalid and Desktop removes the account itself, the assignments are kept.

Commit identity is a separate matter​

This is the gotcha worth underlining. GitHub's documentation says the assigned account doesn't change the name and email Git uses as the author of your commits. The account controls access. It does not control authorship.

If you commit to work repos with your personal email, nothing in this feature fixes that. You'll still want to check your Git name and email settings in Desktop, or per-repository Git configuration where appropriate. This is my practical reading of the documentation, not a tested scenario. For consultants and contractors, it's the difference between "authenticated correctly" and "attributed correctly".

One Copilot detail​

The docs also note that Copilot features in Desktop, such as generating commit messages, use the repository's account if it has Copilot access. Otherwise they use another signed-in account that does. That is a documented behavior for Copilot features specifically. It shouldn't be read as meaning every feature switches accounts this way.

Analysis: who benefits, and what to watch​

The biggest winners are people with a personal and a work identity on GitHub.com, freelancers with client accounts, and enterprise users spanning several GHE.com or Enterprise Server identities. The changelog's "no fixed limit" claim is generous, though a long account list will mean more dropdown choices. The "always asked on public repos" rule can also feel slightly nagging when you have several accounts. That's the price of Desktop not guessing which identity you want.

Existing workarounds will not necessarily need removing. If you've embedded SSH aliases or tokens in remote URLs, test one repository after upgrading before ripping anything out. The documentation covers HTTPS authentication, so don't assume the new assignment replaces SSH-based routing. That's a caution rather than a documented finding.

Bottom line​

GitHub Desktop 3.7.0 removes a long-standing friction point. Update, add your second account under Options > Accounts, and check each repository's assignment under Repository settings > Remote. Then confirm your Git author name and email, because that setting is still separate.

 

References

  1. GitHub Desktop now supports multiple accounts per host GitHub Changelog 2026-11-20T02:06:01+00:00
  2. Using multiple accounts in GitHub Desktop - GitHub Enterprise Cloud Docs docs.github.com
  3. How to Manage Multiple GitHub Accounts on the Same Machine multilogin.com