Skip to main content
Let’s take a step back and review the different GitHub accounts and browser setup I’ll use throughout this guide.
A presentation slide titled "GitHub Personal Accounts" on the left with a large blue curved shape on the right containing the word "Demo." The bottom-left corner shows "© Copyright KodeKloud."
I use the Firefox browser because it supports the Firefox Multi-Account Containers extension. This extension isolates cookies and session data by container, so you can remain signed in to multiple GitHub accounts in the same browser window without switching profiles or opening multiple private windows.
Firefox Multi-Account Containers helps when you need to switch quickly between accounts (for example, an admin and one or more developer accounts) while keeping each session isolated.
Below are the containers I created for this demonstration and their intended uses: How to verify which account/container is active:
  • The container name appears in the tab/address bar when a container is active (for example, “AliceAdmin”).
  • Each container is color-coded so you can identify sessions visually.
  • Look at the tab icon and label to confirm you’re using the intended account before performing administrative or destructive actions.
Quick tips for working with multiple GitHub accounts:
  • Use separate containers to avoid cross-account cookie/session conflicts.
  • Pin or bookmark frequently used pages inside their respective container to reduce accidental cross-usage.
  • When testing permissions or workflows, open one window with multiple tabs (each in its container) so you can replicate user interactions quickly.
Useful links and references:
Avoid performing admin-level changes while signed in to a developer container. Always confirm the active container label and color before making configuration or access changes.

Watch Video