✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Two-Factor Authentication: enrolment & method tables

The Two-Factor Authentication plugin stores per-user enrolment in wp_usermeta under tfa_ keys and policy in wp_options. SleekView joins that to wp_users so 2FA coverage across roles becomes one queryable table.

♾️ Lifetime License available

SleekView table view for Two-Factor Authentication

Audit 2FA enrolment across every role

The Two-Factor Authentication plugin stores per-user 2FA configuration in wp_usermeta under tfa_ prefixed keys (configured algorithm, secret, last used codes), and plugin policy in wp_options under tfa_ rows. The default admin presents per-user setup on each user's own profile screen, with policy in plugin settings, and no combined view of who is enrolled across the site.

SleekView reads the tfa_ user meta as columns joined to wp_users, so a single table shows user, role, configured algorithm (TOTP, HOTP, fallback), last login from user_meta, and recovery code state. Sort by role to spot admins still missing 2FA, filter to authors using older fallback methods, or pull users created in the last 30 days that haven't enrolled.

Inline actions, like clearing a user's tfa_secret to force re-enrolment or marking a recovery code consumed, route through the plugin's own functions where supported. SleekView is read-mostly, so the plugin remains the authoritative source for 2FA state, and the security lead finally gets the audit table the plugin doesn't ship with.

Workflow

From scattered profile screens to one enrolment audit

1

Map the tfa user meta

SleekView registers tfa_configured_algorithm, tfa_secret, and tfa_recovery_codes as columns joined to wp_users, with policy options from wp_options as a separate source.
2

Build the audit view

Pick user, role, algorithm, last login, and recovery code count. Save filter sets like 'Admins missing 2FA' and 'Recovery codes under 3' for repeatable reviews.
3

Scope per role

Give support staff a read-only audit view, and grant security leads inline reset rights. Policy settings stay restricted to administrators.
4

Act inline

Reset a tfa_secret, force re-enrolment, or refresh recovery codes from a row. Writes flow through the plugin's own functions.

Sample columns

A typical Two-Factor Authentication enrolment view

Users with their configured 2FA algorithm, role, and recovery state in one row.
Source: wp_usermeta (tfa_*) + wp_options (tfa_*) + wp_users
User Role Algorithm Last login Recovery codes Status
alex@studio.co Administrator TOTP Apr 24 5 left Enrolled
ria@design.io Editor HOTP Apr 23 2 left Low codes
tom@hello.dev Author TOTP Apr 19 0 Refresh codes
mia@brew.coop Subscriber None Apr 18 Not enrolled

Comparison

Default Two-Factor Authentication admin vs SleekView

Default Two-Factor Authentication

  • Per-user state lives in profile screens, not a sortable table
  • tfa_* user meta is invisible to anyone who isn't writing SQL
  • Hard to spot admins still missing 2FA across the site
  • Recovery code state isn't exposed as a column
  • Forced re-enrolment requires editing each user's profile

SleekView

  • Reads tfa_* user meta as columns joined to wp_users
  • Filter to admins missing 2FA or users with zero recovery codes
  • Sort by algorithm to see who is on TOTP vs older fallback
  • Inline reset of tfa_secret via the plugin's own functions
  • Save views like 'Editors without 2FA this month' and reopen them per audit

Features

What SleekView gives you for Two-Factor Authentication

tfa user meta as a real table

tfa_configured_algorithm, tfa_secret, and tfa_recovery_codes become sortable columns joined to wp_users. The audit becomes a single screen instead of a chore.

Filter by role and algorithm

Combine role, algorithm, and recovery code count to surface accounts that need a follow-up. Useful before flipping a forced enrolment policy in wp_options.

Reset inline

Clear a user's tfa_secret or invalidate recovery codes from a row. Writes route through the plugin's own actions so the audit log stays correct.

Audience

Who uses SleekView for Two-Factor Authentication

Security leads rolling out 2FA

Audit enrolment across roles and reach full administrator coverage before flipping a forced policy. The 'Admins missing 2FA' saved view is the rollout dashboard.

Support staff

Verify a user's enrolment from one row, reset their tfa_secret inline when they lose access, and confirm the change without leaving the table.

Auditors and compliance reviewers

Filter to users with zero recovery codes, export the slice to CSV, and produce evidence of 2FA coverage for a SOC2 or ISO review without screenshots.

The bigger picture

Why 2FA rollouts stall without an audit table

Most 2FA rollouts get stuck because the security lead can't see the gap they're trying to close. The Two-Factor Authentication plugin records enrolment state in wp_usermeta under tfa_ keys and policy in wp_options, which is the right place architecturally but the wrong place for a person trying to audit coverage. The default admin treats 2FA as a per-user setting, so the only way to know how many administrators still aren't enrolled is to click through every profile or write a SQL query.

SleekView reads the user meta as a real table and turns that question into a saved view. Support staff get a read-only slice for handling individual lockouts, while a security lead gets the audit view that drives the rollout itself. Auditors get a CSV with role, algorithm, and recovery code state preserved as evidence.

The plugin keeps writing the data; SleekView just gives the people running the rollout a working surface to read it in the order they need. Once enrolment is visible at a glance, the gap closes quickly.

Questions

Common questions about SleekView for Two-Factor Authentication

This page describes the Two-Factor Authentication plugin that stores per-user state in wp_usermeta under tfa_ prefixed keys (most commonly the Simba Hosting / David Anderson plugin family). The same approach works for any 2FA plugin that uses user meta, and SleekView can be reconfigured to read different meta keys if you're on a fork.

 

Yes. SleekView calls the plugin's own reset action on a row, which clears tfa_secret and re-prompts the user to enrol on the next login. The plugin's own audit log reflects the reset.

 

Recovery code state is exposed as a count column, not the codes themselves. The view shows how many codes remain on tfa_recovery_codes per user, so accounts close to zero codes can be reminded before they lock themselves out.

 

No. It only reads what the plugin already stores in wp_usermeta and wp_options. Writes happen exclusively through the plugin's own functions, so it remains the authoritative source for 2FA state.

 

Yes. Any filtered view exports to CSV from the table header. User, role, algorithm, and recovery code count are preserved exactly as shown for compliance evidence.

 

Yes. Saved views can be assigned per WP role, so support staff see only the users they handle, while security leads see the full enrolment table. The plugin's own capability checks still gate writes.

 

No. The view shows enrolment state, not secret values. tfa_secret contents are never rendered in the table, so the audit is safe to share with reviewers.

 

Yes. 2FA state is per site context where applicable, and SleekView respects the active scope. Network admins can build cross-subsite audits; subsite admins see only their own users.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView