Why one auth flow doesn't fit every role
A consumer logging into an app, a merchant-desk operator starting a shift, and an administrator making high-impact changes all carry different risk levels — treating them with identical authentication either over-burdens low-risk users or under-protects high-risk actions.
Scaling requirements to what's at stake
A reasonable pattern scales requirements to risk: lighter authentication (a phone number and OTP, for instance) for routine consumer actions, and layered requirements — a password, a biometric re-proof, a hardware key — for roles that can take sensitive or irreversible actions.
Re-proving identity for sensitive actions
Even an already-authenticated session can be asked to re-prove identity — a fresh face check — before a particularly sensitive action, rather than treating the initial login as a blanket authorization for everything that follows.