What is the main administrative purpose of synchronizing IdP groups to GitHub teams (team synchronization)?
Select an answer to reveal the explanation.
Short Explanation
Team sync keeps GitHub team membership honest with your directory groups. When people join or leave an AD/Okta group, GitHub teams follow, cutting manual owner toil and stale access grants. It's directory alignment, not a VCS protocol change.
Full Explanation
The correct answer is mapping identity provider groups to GitHub teams so membership remains aligned with corporate directory state. Team synchronization reduces manual adds and removes and improves joiner-mover-leaver hygiene for repository access mediated by teams. The option about compiling Git clients from source on every laptop is unrelated. The option about replacing Git history rewriting tools is unrelated to access management. The option about forcing all repositories to use SVN bridges is false. Design group strategy carefully (least privilege teams, avoid oversized catch-all groups), monitor sync failures, and remember that org roles like owner still need deliberate assignment beyond simple team sync.