Members List builds its directory by querying wp_users with optional joins into wp_usermeta for profile fields like city, company, or signup source. The plugin renders the directory on the front end, the admin screens only configure layout and visibility. The headline question, who joined this week, lives on the WordPress Users screen, not where the directory does.

SleekView reads wp_users joined to wp_usermeta and surfaces the same fields the directory uses, plus user_registered for sorting and filtering. Each row is one member with role, profile metadata, and registration timestamp.

Members List keeps owning the front-end rendering. SleekView only adds the in-admin table, so saved views like New members this week or Members in Berlin become a one-click reopen instead of a database query.

Members List does the rendering, but a public directory is not an admin tool. Without an in-admin table, the team relies on screenshots and ad-hoc counts to answer questions a community update should make trivial. SleekView reads the same wp_users and wp_usermeta rows the directory queries and surfaces them as one sortable, filterable workspace.

The plugin keeps owning the directory output, SleekView just answers the count and filter questions inside WP Admin. Saved views travel with the site, filtered rows export as CSV when the board needs evidence, and the community manager stops doing spreadsheet math.