Rublon 2FA pairs a WordPress account with a Rublon identity and adds a second-factor challenge (mobile push, security key, SMS, or email link) at login. Per-user enrollment state, method preference, and verification timestamps land in wp_usermeta with the plugin's prefixed keys. The default Users screen does not expose any of this, which makes the operational question 'which administrators still need to enroll' invisible at scale.

SleekView reads wp_users joined with the rublon2fa_* usermeta keys directly. User, role, enrollment status, primary method, and last verified become first-class columns. Filter by role and status to see administrators still without 2FA. Sort by last verified to spot dormant accounts. Save the view and reopen it during the monthly security review with one click.

The plugin keeps owning the Rublon identity link, push approvals, and method enforcement. SleekView adds only the cross-user surface, so audit evidence is a CSV export of a saved view rather than a manually maintained spreadsheet.

Rublon 2FA shines at the second-factor experience: push approvals on a phone, security-key support, and a clean recovery story. The trade-off is that the per-user state it writes to wp_usermeta is not surfaced on the WordPress Users screen, so the cross-user audit question is buried under per-user clicks. SleekView reads the rublon2fa_* meta keys the plugin already writes and joins them onto wp_users to produce a roster with role, status, method, last verified, and trusted-device count on a single line.

Compliance reviews become a saved view, and the CSV export becomes the audit evidence. The plugin continues to enforce. The security team gains a real cross-user surface inside WordPress without a second tool, without exporting from wp_usermeta by hand, and without a stale spreadsheet that lives outside the install.