No. The free version stores fields the same way in wp_usermeta. Pro just gives you more field types like uploads and repeaters, conditional logic, and add-ons like Admin Approval and WooCommerce Sync. SleekView reads whatever fields exist and surfaces them as columns. Free installs get most of the value, Pro installs unlock the bulk approval action.

Yes. Select rows, pick the Approve action, and SleekView calls the same hook the Admin Approval add-on uses. Notification emails go out, the user becomes active, and the queue count drops. Bulk reject works the same way through the plugin's reject hook. The flow stays inside Profile Builder's logic, so any custom hooks attached still fire.

Serialised values are previewed in the cell with a count. Open the row drawer to edit each entry separately, with the structure preserved. A repeater of skills or availability slots stays a repeater after editing rather than collapsing into a flat string. This matches how the front-end edit-profile shortcode handles the same data.

No. SleekView reads wp_usermeta, so values written by the Profile Builder WooCommerce Sync add-on appear as columns just like any other Profile Builder field. The two add-ons cooperate without overlap. WooCommerce Sync handles the push from WooCommerce checkout to Profile Builder fields, SleekView handles the view on top of the resulting data.

Yes. Apply filters, hit export, and SleekView writes a CSV or JSON of just those rows with the active column selection. A pending-users export becomes the file you hand to legal for review. A by-city export becomes the file you hand to the regional event organiser. The export respects capability gating, so the role doing the export only sees what it is allowed to see.

SleekView is back-end only. Profile Builder Pro handles the front-end User Listing through its own shortcode. The two split responsibilities cleanly: the front-end listing is for visitors and members browsing the directory, the back-end view is for moderators and admins working on the directory. Both read from the same wp_usermeta, so the data is consistent.

The approved status is stored in usermeta by the Admin Approval add-on. SleekView surfaces it as a column with status colours: approved, pending, and rejected. Filtering on the column gives you the moderation queues directly. Bulk actions on the column trigger the add-on's own approval hooks, so emails and capability changes happen exactly as the plugin expects.

Profile Builder stores avatar uploads as attachment IDs in usermeta. SleekView shows the column as Uploaded or Default based on whether the meta key has a value. Opening the row drawer shows the attachment preview. This makes it easy to spot members who never completed their profile by uploading an avatar, often a useful proxy for engagement.