SleekView for WP 2FA
WP 2FA writes enrollment status, method, and grace-period data to wp_usermeta. SleekView surfaces all of it in one live, filterable table so compliance is provable, not just configured.
♾️ Lifetime License available
2FA policies only matter if you can audit them
WP 2FA by Melapress is a strong implementation of two-factor authentication for WordPress, with role-based policies, configurable methods (TOTP, email, backup codes), and grace periods for rollouts. The plugin's settings UI is clean and the user-facing wizard is well thought out. What WP 2FA does not focus on is the auditor's view: a single roster of every user, what method they picked, when their grace period ends, and which admins are still non-compliant.
SleekView reads the wp_usermeta keys WP 2FA writes (typically prefixed with wp_2fa_ for enabled methods, status, and grace data) and joins them with wp_users to produce a per-user compliance roster. Add columns for role, method, enrollment status, and grace expiry. Save the filter that matters most to leadership, like 'Admins without TOTP' or 'Users with grace ending this week.'
The pairing matters because 2FA only counts in audits when you can prove enforcement. Screenshots of WP 2FA's settings page show policy. SleekView's filtered exports show compliance at a per-user level, which is what auditors and security committees actually ask for.
Workflow
From WP 2FA settings to provable compliance
Map the meta keys
Join with users and roles
Save the audit views
Export and report
Sample columns
2FA enrollment by user
wp_usermeta
| User | Role | Method | Enrolled | Status | Grace ends |
|---|---|---|---|---|---|
| dennis | Admin | TOTP | Yes | Compliant | — |
| marie | Editor | Yes | Compliant | — | |
| tom | Editor | — | No | In grace | 2026-05-02 |
| old-admin | Admin | — | No | Non-compliant | Expired |
Comparison
WP 2FA alone vs. WP 2FA + SleekView
Default WP 2FA screens
- Default screens show policy config, not per-user audit at scale
- No filterable column for method chosen
- Hard to identify grace-period stragglers in bulk
- No saved views to share with security leads
- Export of enrollment status is manual
SleekView
- Joins wp_users with WP 2FA usermeta keys
- Filter by enrollment status, method, or role
- Highlight grace-period stragglers automatically
- Saved views for monthly 2FA compliance reports
- Export to CSV for stakeholder reviews
Features
What SleekView gives you for WP 2FA by Melapress
Compliance dashboard
Build a saved view that shows every admin and their 2FA status. Send the filtered CSV to leadership instead of a screenshot collection of WP 2FA's settings page.
Stragglers list
Filter to users whose grace period expires this week. Reach out before the lockout fires and turns a routine policy into a support ticket.
Method audits
Filter by method (TOTP, email, backup codes) to verify your policy guidance is being followed. Spot users still on the weakest acceptable option.
Audience
Where WP 2FA + SleekView is essential
Regulated industries
Financial services and healthcare sites need provable 2FA enforcement. SleekView produces audit-ready evidence without exporting from the database manually.
Large editorial teams
When dozens of editors share access, knowing who is enrolled is non-negotiable. A saved roster view replaces the spreadsheet someone updates by hand.
Agencies
Standardize a 2FA compliance view across every client site you manage. One template, one query, one consistent answer for every retainer review.
The bigger picture
Enforcement is half the story; evidence is the other half
Most security incidents that involve compromised WordPress credentials happen on accounts that should have had 2FA but didn't, often because someone slipped through a grace period or a role exemption that nobody reviewed. WP 2FA's enforcement is solid, but enforcement only works if it is regularly audited at the per-user level, and the default plugin screens emphasize policy configuration rather than per-user state. The result is that security teams either trust the policy is being applied correctly (which auditors don't accept) or they extract enrollment data manually from usermeta.
SleekView turns the underlying data into the asset it should be: a roster of every user and every relevant meta value, joined and filtered, with saved views for the questions a security committee asks every quarter. That moves 2FA from 'we have a policy' to 'here is the proof, exported yesterday, with these specific stragglers being followed up by name.'
Questions
Common questions about SleekView for WP 2FA by Melapress
No. WP 2FA continues to enforce, gate logins, and manage grace periods. SleekView only reads the meta keys WP 2FA writes. The two plugins are completely independent at runtime, so there is no risk of SleekView interfering with login flow or policy decisions.
Yes. WP 2FA stores enabled methods in usermeta under a documented key. Map that key to a SleekView column and the value becomes sortable and filterable. You can build a view that shows only users on the email fallback if your policy expects TOTP as the primary method.
No. SleekView respects the same capability and meta-key restrictions WP 2FA does. Sensitive keys like backup-code hashes can be marked hidden in the column configuration so they never appear in any view, regardless of who opens the SleekView.
Yes. Any extra meta the premium edition writes (additional grace tracking, per-role exceptions, recovery audit fields) can be exposed as columns just like the free plugin's keys. SleekView is plugin-agnostic and reads whatever wp_usermeta contains on your install.
Yes. Network and per-site enrollment can both be queried. On multisite you can build a network-level view that lists every user and their per-site 2FA status, or scope each view to a single blog when each tenant has its own policy.
Reset actions still go through WP 2FA's own controls to keep responsibility clear. SleekView lets you flag users inline for follow-up, export their details to a ticketing system, or annotate the row, but the actual reset remains under WP 2FA's audit trail.
Live. SleekView queries wp_users and wp_usermeta on demand each time the view loads, so a user who enrolled five minutes ago shows up correctly. There is no internal cache to invalidate, which matters during an audit when stale data would undermine the report.
Yes, if WP 2FA writes them. The enrollment-completed-at and grace-started-at meta values can be added as date-typed columns, which makes 'enrolled in the last 30 days' a sortable, filterable predicate rather than something you have to compute by hand.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Yith Woocommerce Product Image Gallery Slider
- Yith Woocommerce Checkout Manager
- Woocommerce Additional Variation Images
- Woocommerce Amazon Pay
- Yith Woocommerce Pdf Invoice
- Yith Woocommerce Affiliates
- Woocommerce Blocks
- Wpc Fly Cart
- Woocommerce Eu Vat Number
- Checkout Field Editor
- Woocommerce Advanced Shipment Tracking
- Shipment Tracking
- Variation Swatches
- Yith Woocommerce Multi Vendor
- Woocommerce Pdf Invoices Packing Slips