The Passwordless Login plugin replaces password prompts with a short-lived emailed token. Each request writes a token row, expiry timestamp, and used flag into WordPress options or per-user usermeta depending on the build. The default plugin screens cover settings and request rate limiting, not the cross-user log of who has been asking for magic links, from where, and how many tokens have actually been used.

SleekView reads the token records directly. User, requested at, expires at, used at, IP, and user agent become first-class columns. Filter to used equals false and expires within the last hour to see the bounce rate of magic links your team is sending. Sort by IP to spot a single address generating bursts of token requests. Save the view and reopen the on-call dashboard with one click.

The plugin keeps owning token generation, email delivery, and the login redemption flow. SleekView adds only the audit surface so the team can see the magic-link activity as data instead of as scattered log lines.

Passwordless authentication is a great fit for content sites and editorial workflows because it removes one of the most common credential-leak vectors. The trade-off is that every link is a short-lived token, and the operational story of those tokens (issued, delivered, redeemed, expired, or replayed) is exactly the audit surface that the default plugin screens do not provide. SleekView reads the plugin's underlying token records, whether they live in wp_options or wp_usermeta, and renders them as a queryable workspace.

Support, security, and compliance teams each get a saved view tuned to their question. The plugin keeps owning generation, delivery, and redemption. The team gets a real audit log inside WordPress without exporting from the database by hand, and the suspicious-burst case stops being something that gets noticed only after a support ticket arrives.