Security Question Reset
A reset password form that verifies identity with a saved security question and answer before allowing a new password. Use as a passwordless recovery path.
A reset password form that verifies identity with a saved security question and answer before allowing a new password. Use as a passwordless recovery path.
Search blocks by description or jump to a page.
Security Question Reset is a four-step recovery card. A centred icon and title sit at the top, beneath a four-segment progress bar that fills as the user advances. Step one collects an email address and username to locate the account. Step two surfaces a "Account Found" summary row with a "Pending Verification" badge, a warning alert, and a security question select with a free-text answer field. Step three shows a green verification alert and two password inputs, each with a visibility toggle. Step four replaces the form with a large success icon, a confirmation message, a "Sign In" button, and a bulleted list of security recommendations. A footer below the card carries a "Sign in instead" link and, on steps two and three, a "Start over" control.
The card holds all four steps in a single container, so you can adjust the copy at each step, swap or trim the list of security questions, and remove the recommendations panel without touching the step logic. The progress bar, icon, and description update automatically based on the active step.
Reach for this block when your product stores a security question on signup and you want to offer a recovery path that works without email access. It suits developer tools platforms where CLI or API users may have unstable email delivery but know their account credentials well. It is a better fit than the Email OTP Reset when email is unreliable, and a better fit than the Simple Reset when the reset link flow is unavailable or you need an extra identity check before allowing a password change.
A natural flow around it on an Application page:
Before
After
The block covers the full self-service recovery journey in one card, and each step is independently editable:
Tip: if your backend returns the specific question tied to the account rather than letting the user choose, replace the Select with a read-only field so users cannot cycle through questions until one matches.