Administration scoped to what actually needs administering
A scoped admin role grants administrative authority limited deliberately to a specific subset of an organization — a single team, a single department, a single region — rather than to the organization as a whole. A team lead can administer their own team's membership and settings without holding any authority over any other team, which lets administrative work be delegated to the people genuinely close to it without each delegation also handing over organization-wide reach that the actual task never required.
This is a direct application of least privilege to administration specifically: the task that needs doing is managing one team, so the access granted should cover exactly that team, not the entire organization simply because 'administrator' was the closest role available on the menu.
Why the underlying permission model has to support this natively
Getting the boundary right requires the underlying system to actually support this kind of scoping, rather than treating 'administrator' as a single, all-or-nothing designation with no intermediate option. A system offering only full organization-wide admin or no admin at all forces every delegation to be broader than it needs to be, which accumulates over time into exactly the kind of unnecessary standing access that's cheap to grant in the moment and expensive later — even when nothing goes wrong with any individual grant along the way.