Find a sign-in event
The journal helps investigate access and security issues.
How to use it
- Open the registration and sign-in journal.
- Find a user by name or email and set an event filter.
- Check the time, sign-in method, device and session status.
Advice and practical context
The journal supports focused investigation
Sign-in events answer a specific support question: who signed in, when, by which method, and what happened to the session.
Example of investigating a report
Example: for an unfamiliar-login report, an administrator narrows the period, checks user and device, and records only facts needed to resolve it.
Start an investigation with the exact interval and event type reported in the case. A matching email helps locate the user, but the conclusion should consider time, sign-in method, device and session state together. State the time zone in a support response. Do not export neighboring events for unrelated people or use the journal to profile interests or ordinary user behavior.
Do not turn the journal into behavior analytics
Security events contain sensitive context. Do not publish them or use them beyond support and account protection.
Technical detailsCalculations, permissions and behavior
Registration and login journal
Registration and session creation are written to a separate append-only journal. For existing accounts, MARPLA safely backfills user and current-session records without duplicates. Each row shows Europe/Lisbon time, event type, user, sign-in method, IP, a readable device label and session state.
The full User-Agent is available only to the administrator on hover. Signing out or session expiry changes the state but does not remove the journal event.
Personal data and search
Email, IP and device data are used only for security and sign-in support. They are available only to system administrators and never enter game teams, the public marketplace or investor links. Search runs on the server, results are limited to forty rows per page, and the page is marked no-index.