Wishlist Registration is the registration extension that pairs with Wishlist Member to capture sign-ups and (when enabled) route them through an approval workflow before level access is granted. Registration rows land in wp_wlm_userlevels with the user_id, the level_id requested, a status column for pending, active, or rejected, and timestamps for registration and last update. Extra registration-form fields are stored in wp_usermeta keyed by the form-field slug.

The default admin shows a Pending Members tab, which is fine for low-volume approvals. Higher volume sites need cohort views: every pending registration from this week, every approval awaiting review for more than 48 hours, every registration with a specific referrer or signup source. The default Pending tab doesn't sort or filter on those dimensions, so ops either clicks one user at a time or runs custom queries.

SleekView reads wp_wlm_userlevels directly, joins wp_users for contact email, joins wp_usermeta for the registration-form fields, and turns the approval queue into a sortable, filterable table. Inline approve or reject calls Wishlist Member's own functions so the welcome email and capability sync still fire. Bulk approval across a filtered cohort is one click rather than per-user.

Approval workflows look simple until volume rises and the default Pending tab stops being enough. The questions ops actually asks (which registrations came from the affiliate program this week, which have been waiting more than 48 hours, which form-field values mark a registration as legitimate) are cohort questions and the default tab is a per-user list. Wishlist Registration stores everything needed to answer them, in wp_wlm_userlevels for status and timestamps and in wp_usermeta for the form-field values.

SleekView turns the queue into a sortable, filterable table where those cohort questions are single saved views. Approval ops can run a daily pass in minutes; support can see per-registrant context without leaving chat; community ops can audit channel quality by source. For sites running stricter approval rules (paid memberships, gated communities, regulated content), the visibility shift turns hours of per-user clicks into one bulk-approve action across a filtered cohort.