Yes, including text, select, multi-select, date, and file upload fields. File fields render as a download link. Conditional fields, profile pictures, and rating fields are also supported. The detection runs against the UserPro fields screen, so anything you can register through UserPro becomes available as a column without any extra configuration.

Yes. Every field you add as a column is filterable, with type-aware inputs. Date fields get a date picker with relative ranges, select fields get dropdowns, numeric fields get range sliders, and text fields get contains and exact match modes. Combining filters builds compound queries no single UserPro screen offers.

Yes. Pending verification rows can be approved or rejected inline and the UserPro hooks fire as expected. Approval emails go out, role changes apply, and any custom verification logic you have hooked into UserPro keeps running. Bulk actions dispatch the same hooks one row at a time, which keeps the audit trail clean.

Yes. Drop the SleekView block on a page and use role-based column visibility to hide private fields. Visitors see public profile data, members see additional fields like contact info, and admins see everything including verification flags. The same table view powers all three audiences with different visibility rules.

Yes. Connection counts and follower data exposed in usermeta can be added as columns. Sort by follower count to find the most-connected members, or filter to find users with zero connections for re-engagement campaigns. Activity stream metadata is also surfaceable as last-action timestamps.

Yes. SleekView checks the same capability rules UserPro uses, so editors only see what they should. A moderator with edit_users permission can update profile fields, while a content editor without that permission gets a read-only view. The capability check happens server-side on every save, so you cannot spoof an edit by manipulating the table client-side.

Not in moderation mode. SleekView is built around admin-grade and role-scoped views rather than self-service editing, so a member updating their own profile should still use the UserPro frontend forms. You can show them a read-only view of their own data alongside the directory if you want to combine the two patterns on one page.

Filter to the requesting user, hit CSV export, and you get every column visible in the table including custom fields. For full-record exports including private internal fields, give the export a temporary admin-scoped view with all columns visible, run the export, then delete the view. The generated CSV satisfies most subject access request workflows.