Use Sign-in activity to compare recorded accounts and addresses. The view summarises repeated use of an address; it is not a separate row for every session.

Read the two lists

1. Open PD Modules → Guard → Sign-in activity.
2. Review Admin sign-ins and Customer sign-ins separately.
3. Search the relevant account or address and compare Sign-ins, First seen where present, and Last seen.
4. Check the correct client association before opening a customer profile.

Each list loads the latest 50 account/address records before its on-screen searching and sorting. A search with no result does not prove that an older address was never used. The sign-in count accumulates repeated successful observations for the same account/address pair.

Interpret location and identity carefully

Country is derived from the observed address when available; it is not a verified traveller location or a unique device identity. The country column may be omitted when none of the loaded customer records has a value. Do not infer a broken recording feature merely from an absent country.

Administrator history depends on Alert on admin login. Customer recording depends on Record client login history. Neither setting reconstructs activity from before recording was enabled. An empty view can also reflect unavailable data, so check the setting and a relevant legitimate event before making a security conclusion.

Keep the review private

Only share the minimum redacted rows needed for investigation. These lists include private identities and addresses.

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