Yes. Every field registered through the WP-Members fields screen is detected automatically. Text, dropdown, multi-select, date, file upload, and hidden fields all become column options. Type-aware filters appear based on the field type, so date fields get date pickers and dropdowns get multi-select filters without any manual configuration.

Yes. Filter to pending, select all, and approve. SleekView calls the WP-Members approval API row by row so notification emails go out, role changes apply, and any custom approval logic you have hooked in keeps running. The bulk action processes hundreds of approvals in a single batch with the audit trail intact.

Yes. Status changes fire the standard hooks so any notification add-on still works. Welcome emails on approval, expiry warnings, and password reset flows all continue to function because SleekView never bypasses the WP-Members update API. If a notification is conditional on specific field changes, the same conditions apply to inline edits as to manual edits.

Yes. Membership levels, user profile, and custom redirect add-ons all expose data SleekView surfaces as columns. Multi-tier membership levels become a tier column with multi-select filtering, custom redirects appear as a redirect URL column, and any add-on writing to usermeta or custom tables can be configured as a data source.

Yes. Use role-based column visibility to show a public directory while hiding admin-only fields. Members see name, company, and public profile fields, while admins see approval status, internal notes, and renewal data. The same underlying view drives both audiences with different visibility rules per role.

Yes. Whatever columns are visible in the table show up in the export, custom fields included. Filter to the rows you want, configure the visible columns, and the export matches exactly what you see. This removes the need for a separate export plugin and keeps custom field data accessible for renewal campaigns or finance reconciliation.

If WP-Members or your add-on stores multiple levels in a single meta field, surface it as a multi-select column with the appropriate filter. Each member's row shows all their levels, and filters work with any-of or all-of semantics. For setups using separate meta fields per level, expose each as its own column to make tier-by-tier reporting precise.

Yes via custom row actions. Filter to expiring-soon members, select all, and trigger a custom action that fires the WP-Members reminder hook or calls your email tool's API. The action runs server-side row by row, which keeps email rate limits respected and gives you a clean log of who was reminded when. Combine with saved filter presets to make this a weekly task.