miniOrange 2FA owns the policy, the wizard, and the enforcement at login time. The per-user state (enrolled or not, method picked, enrollment date, last verification) is written to wp_usermeta with the plugin's prefixed keys. The default WordPress Users screen shows username, role, email, and post count, none of which answer the question leadership actually asks: which administrators still have not enrolled.

SleekView reads wp_users joined with the miniOrange 2FA usermeta keys directly. One row per user, with role, status, method, enrollment date, and last login as filterable columns. Filter to role equals administrator and status equals not enrolled to see the compliance gap in one view. Sort by enrollment date to see who registered late. Save the view and reopen it monthly when the audit closes.

The plugin keeps owning enforcement, prompts, and method support. SleekView only adds the cross-user roster surface, so compliance review takes minutes instead of stitching together a CSV export with a spreadsheet pivot.

miniOrange 2FA does the hard part well: enforcement, method support, and the user-facing wizard. The trade-off is that per-user state lives in wp_usermeta and never reaches the Users screen, so the simple question 'which admins still have not enrolled' becomes either per-user clicks or a CSV export with spreadsheet pivot. SleekView reads the usermeta keys the plugin already writes and joins them onto wp_users, so the answer is a one-click saved view.

The plugin continues to enforce. The security team gets a compliance roster, audit-ready exports, and rollout tracking inside WordPress, without a second tool and without exporting anything the team did not already capture.