Let customers see recent recorded addresses for their own account and receive an email when an address is new to that signing-in user. Customer emails are separate from staff alert recipients.

Review both controls

1. Open PD Modules → Guard → Settings.
2. Enable Record client login history if you intend to collect future customer sign-ins.
3. Review Email clients on a sign-in from a new address separately.
4. Choose Save settings.
5. Use an authorised account and non-sensitive sample data to check future legitimate activity and customer visibility.

The recording switch is required for this new-address email path. Keeping the email option enabled while recording is off does not produce those alerts. Earlier rows are not erased by turning recording off, and the existing customer panel can still show saved history.

What the customer sees

The client-area Recent sign-ins panel shows up to five recent account/address records. These are grouped observations with a last-seen time, not a chronological list of every login session. An absent or older row does not prove no sign-in occurred.

Recording resolves the signed-in user to its client account. Check that association if the expected customer panel or email is missing.

Diagnose email separately

An email is attempted for a newly recorded user/address pair with a resolved client association. It goes through PD Guard New Sign-In Alert rather than the staff recipient list. The record can exist even if sending fails, so the next sign-in from that known address may not generate a replacement email.

A changing public IP can produce a new-address message for the same device; another device behind a shared address may not. For an unexpected result, check the association, time, switches and mail evidence.

See the PD Guard Blesta guide for related tasks, or explore PD Guard.