AddThisFeature

Login Attempt Alerts

Tell the account owner when a sign-in looks like it needs their attention.

moderate Security & Reliability

What it adds

Notifications to the account owner about new-device sign-ins and bursts of failed attempts, with a direct path to lock the account down.

What your agent is told to do

5
  1. 1

    Alert on the events that actually matter: a successful sign-in from an unrecognised device, and a burst of failed attempts against the account.

  2. 2

    Include the time, approximate location, browser, and platform, and state plainly what to do if it was not them.

  3. 3

    Link to session revocation and password change, and require the user to authenticate before either — the alert link must never be a credential itself.

  4. 4

    Deduplicate: one risk event produces one alert, and repeat alerts for the same device or the same failure burst are collapsed within a window.

  5. 5

    Do NOT alert on every IP change. Mobile networks, VPNs, and corporate proxies rotate addresses constantly, and an alert users learn to ignore protects nobody.

Edge cases it handles

6
  • IP geolocation is frequently wrong by hundreds of miles. Say the country or region, never a street-level claim.
  • A user with a rotating VPN will trip a naive new-device rule on every sign-in — key recognition to a stored device token, not to IP.
  • Alerts about failed attempts must not confirm whether the password was close, or whether the account exists.
  • Send the alert to a verified address; delivering a security alert to an unverified or recently changed email hands it to the attacker.
  • If the attacker changed the email first, notify the previous address too.
  • Let the user turn down new-device alerts, but never turn off the alert for a password or email change.

Definition of done

8
  • New-device sign-ins and failed-attempt bursts generate alerts.
  • Alerts include time, device, and approximate region without over-precise location.
  • Repeat alerts for the same risk event are deduplicated within a window.
  • Alert links require authentication before any account change.
  • Alerts go only to verified addresses, and email changes notify the old address.
  • Routine IP rotation does not trigger alerts.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.