2.1. GitHub Accounts, Organizations, and Enterprise
Every action on GitHub happens under some account, and the exam expects you to know which tier of account is doing the work — because permissions, billing, and available features all change depending on the answer.
💡 First Principle: GitHub scales access through three nested account types — personal accounts, organizations, and Enterprise — each adding a layer of shared control over the one below it. A personal account is owned and controlled by one person; an organization groups multiple personal accounts under shared repositories, teams, and billing; and Enterprise groups multiple organizations under centralized policy, security, and billing for a whole company.
You don't choose one tier instead of the others — they compose. A single person can belong to a personal account, be a member of several organizations, and have some of those organizations live inside one Enterprise. Repositories can be owned by a personal account or by an organization, but never directly by an Enterprise — Enterprise sits one level up, governing the organizations underneath it.
| Personal Account | Organization | Enterprise | |
|---|---|---|---|
| Owned by | One individual | Shared, no single owner | A company |
| Contains | Its own repositories | Repositories + teams + members | Multiple organizations |
| Best for | Individual projects | A team or product | A whole company's GitHub usage |
| Central policy? | No | Org-level settings only | Enterprise-wide policy across orgs |
⚠️ Exam Trap: A repository belongs to a personal account or an organization — never directly to an Enterprise. Enterprise governs organizations; it doesn't hold repositories itself.
Reflection Question: If a company has three product teams, each with its own GitHub organization, what does grouping all three under one Enterprise account actually add that the three organizations didn't already have on their own?
