7.6. Reflection Checkpoint

Key Takeaways

• 2FA supplements a password with a second factor; a passkey is a phishing-resistant credential that can replace the password entirely — they solve overlapping but distinct problems.
• Permission roles (read/write/admin) control what an account can do; repository visibility controls who can see it — they're independent settings, both need to be right.
• Enterprise Managed Users shifts account ownership to the company's identity provider, trading personal account portability for centralized lifecycle control.
• Repository visibility (public/private/internal) and branch protection rules are separate layers — a private repository with no branch protection still allows unreviewed pushes to main.
• Teams group members for bulk access management and can be nested to mirror an org chart; team-based access stays current automatically as membership changes.

Connecting Forward

Phase 8 closes out the domain content by looking outward: open source, GitHub Sponsors, the GitHub Marketplace, InnerSource, and the discovery tools (forks, templates, topics) that connect a project to the wider GitHub community.

Self-Check Questions

• Why does the exam draw such a sharp line between "who can see this repository" and "what can someone with access actually do to it"?
• What specific risk does Enterprise Managed Users reduce that a normal organization membership model doesn't?