
- The extension isolates cookies and sessions into separate “containers” so you can be logged into multiple accounts for the same site (e.g., github.com) without interference.
- Each container has a distinct color and label shown in the tab/address area, making it easy to tell which account is active.
- AliceAdmin — GitHub Enterprise administrator account used to configure the org, policies, and user roles.
- KabirDev1 — developer/test account.
- SidDev2 — another developer/test account.
Recognizing which account is active
- Look at the container color and label in the tab or address bar — that indicates the session you’re using.
- When I demonstrate actions, watch for the container name and color to know whether the step is performed as an admin or a developer.
- Use separate containers for admin vs developer tasks to avoid accidental privilege escalation or session leaks.
- Keep one container dedicated to high-privilege accounts (organization owner, enterprise admin) and other containers for developer/test users.
- When testing policies, perform verification from both admin and developer containers to confirm expected behavior.
Tip: Use separate containers for different roles (admin vs developer) to avoid accidental cross-account actions and cookie/session leaks.