SleekView for miniOrange Google Authenticator: 2FA enrolment tables
miniOrange Google Authenticator stores enrolment state in wp_usermeta under mo2f_* keys and plugin settings in wp_options. SleekView reads them alongside wp_users so 2FA coverage by role becomes one queryable table.
♾️ Lifetime License available
Track 2FA coverage by role at a glance
miniOrange Google Authenticator keeps per-user enrolment state in wp_usermeta under keys like mo2f_configured_2FA_method, mo2f_secret, and mo2f_bypass_codes, with plugin configuration in wp_options under mo2f_ prefixes. The default admin presents enrolled users on one screen and policy settings on another, with no combined view of who is configured for which method or who hasn't enrolled at all.
SleekView reads the mo2f_* user meta as columns joined to wp_users, so a single table shows user, role, configured method (TOTP, OTP over email, security questions, KBA), last login from user_meta, and bypass code state. Sort by role and method to see admins without TOTP, filter to authors using the weaker fallback methods, or pull recently created users that haven't completed enrolment yet.
Inline actions, like resetting mo2f_secret or forcing re-enrolment, route through miniOrange Google Authenticator's own functions so the audit trail in the plugin remains correct. SleekView is read-mostly: the plugin keeps writing its own data, and SleekView just gives the security lead the audit table the plugin doesn't ship with.
Workflow
From scattered user meta to one enrolment table
Map the mo2f user meta
mo2f_configured_2FA_method, mo2f_secret, and mo2f_bypass_codes as columns joined to wp_users, with the policy options in wp_options as a separate source.
Build the enrolment view
Scope per role
Act inline
Sample columns
A typical miniOrange Google Authenticator enrolment view
wp_usermeta (mo2f_*) + wp_options (mo2f_*) + wp_users
| User | Role | Method | Last login | Bypass codes | Status |
|---|---|---|---|---|---|
| alex@studio.co | Administrator | TOTP | Apr 24 | 4 left | Enrolled |
| ria@design.io | Editor | OTP over email | Apr 23 | 0 | Weak method |
| tom@hello.dev | Author | Security questions | Apr 22 | 2 left | Weak method |
| mia@brew.coop | Subscriber | None | Apr 18 | — | Not enrolled |
Comparison
Default miniOrange Google Authenticator admin vs SleekView
Default miniOrange Google Authenticator
-
Enrolment state lives in
wp_usermetaundermo2f_*keys, not in a sortable table - No native view of which roles still lack TOTP coverage
- Bypass code state isn't exposed as a column joined to users
- Hard to spot users still on weaker fallback methods like security questions
- Forced re-enrolment requires row-by-row navigation
SleekView
-
Reads
mo2f_*user meta as columns joined towp_users - Filter to admins without TOTP or users with zero bypass codes
- Sort by configured method to see who is still on email OTP or security questions
-
Inline reset of
mo2f_secretvia the plugin's own functions - Save views like 'Admins missing TOTP' and reopen them each audit cycle
Features
What SleekView gives you for miniOrange Google Authenticator
User meta as a real table
mo2f_configured_2FA_method, mo2f_secret, and mo2f_bypass_codes become first-class columns joined to wp_users. No more poking around user profiles one at a time.
Filter by role and method
Combine role, configured method, and bypass code count to surface the accounts that need a stronger setup. Useful before flipping a forced TOTP policy.
Reset and re-enrol inline
Reset a user's 2FA secret or invalidate bypass codes from a row. Writes route through miniOrange Google Authenticator's own functions so the plugin's state stays consistent.
Audience
Who uses SleekView for miniOrange Google Authenticator
Security leads enforcing TOTP
Audit who is on TOTP, who is on weaker fallback methods, and who is unenrolled. Reach full admin coverage before flipping mo2f_ policy settings.
Support staff
Verify a user's enrolment from one row, reset mo2f_secret inline when they lose access, and confirm the change without leaving the table.
Auditors and compliance reviewers
Filter to users with weak methods, export the slice to CSV, and produce real evidence of 2FA coverage by role for a SOC2 or ISO review.
The bigger picture
Why 2FA coverage stalls without a real audit table
Most 2FA rollouts get stuck at the same point: the security lead can't actually see who is and isn't enrolled without clicking through user profiles one by one. miniOrange Google Authenticator records the data in the right place, wp_usermeta under mo2f_* keys, alongside policy in wp_options, but the default admin treats enrolment as a per-user setting rather than a list to audit. The moment a CISO asks 'how many administrators are still on email OTP or unenrolled', the only honest answer is a spreadsheet export and a manual cross-check.
SleekView reads the user meta as a real table and lets that question become a saved view. Support staff use a read-only version to verify enrolment during a support call, while a forced policy is being prepared. Auditors get a CSV that's ready to file.
The plugin keeps writing the data; SleekView just gives the people responsible for the policy a 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 miniOrange Google Authenticator
Yes. miniOrange Google Authenticator stores enrolment in wp_usermeta under the same mo2f_* keys in both free and premium tiers, and SleekView reads from those user meta keys directly.
Yes. SleekView triggers the plugin's own reset action on the row, which clears mo2f_secret and re-prompts the user to enrol on the next login. The audit trail in the plugin reflects the reset.
The configured method is read from mo2f_configured_2FA_method and exposed as a filterable column. A view can isolate users on OTP over email, security questions, or KBA so they can be migrated to TOTP.
No. SleekView only reads what miniOrange Google Authenticator already stores in wp_usermeta and wp_options. Writes happen exclusively through the plugin's own functions, so it remains the authoritative source.
Yes. Any filtered view exports to CSV from the table header. User, role, configured method, and bypass code count are preserved, ready for a compliance file.
Yes. Saved views can be assigned per role, so support staff see only users they support, while security leads see the full enrolment table. miniOrange's own capability checks still gate writes.
It exposes state, not values. The view shows how many bypass codes remain on mo2f_bypass_codes for a user, not the codes themselves, so the audit is safe to share with reviewers.
Yes. Enrolment state is per user and per site context where applicable. SleekView respects the active scope, so a network admin can audit across subsites while 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.
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
- Woocommerce Payu Gateway
- Retainful
- Woocommerce Sendcloud
- Yith Woocommerce Stripe
- Woocommerce Bol Com
- Funnelkit Stripe Gateway
- Authorize Net
- Woocommerce Allegro Pl
- Woocommerce Braintree
- Edd Fes Frontend Submissions
- Lemonsqueezy Wp
- Woocommerce Follow Up Emails
- Woocommerce Stock Manager
- Woocommerce Snapchat Pixel
- Wp Crowdfunding