The preference is stored on the device, keyed by the identifier being used, so a shared machine does not hand one person's default to the next. It is a convenience default, never a restriction — the method picker stays one click away.
Also called: text me the code · login code · sign in method · password or code · verification
- 1The chosen first-factor method is remembered per identifier on that device
- 2The sign-in screen opens on that method
- 3The picker remains available, so the default can never restrict anyone
A crew leader who wants a texted code every time had to hunt for 'use another method' every time, and in the meantime a code went somewhere the screen never named — he would sit waiting for a text while an email he could not see was already sent. The sign-in screen now opens on whatever method that person used successfully last time. It is remembered on the device rather than looked up by email, because that lookup happens before anyone has proved who they are and would let a stranger probe which sign-in methods an address has. If the remembered method is no longer on offer, the picker comes back — it is a default, never a restriction.
- Sign-in forgets the user's preferred verification method on every visit
- Storing the preference server-side would let strangers probe which methods an email supports
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →