Yes. As long as the plugin writes values into wp_usermeta, SleekView can read them. The free version handles the basics and SleekView turns them into columns. The Pro features add more field types, conditional logic, and additional integrations, all of which write into the same usermeta keys. SleekView surfaces them automatically once they exist.

Yes. SleekView writes back to wp_usermeta through the standard update_user_meta function, so the next time the user views their profile they will see the change. Plugin hooks attached to user meta updates still fire. Direct table writes are reserved for fields that have no plugin function, which keeps integrity intact.

Serialised values are shown as collapsed JSON in the cell. Open the row drawer to edit individual entries one at a time, with the structure preserved. The drawer respects the original field shape, so a repeater of address rows stays a repeater of address rows after editing rather than collapsing into a flat list.

Yes. Point a SleekView at the user_registration custom post type to manage your forms in the same table style. You see each form, its fields, its created date, and any custom meta the plugin attaches. This is useful for site operators who run dozens of registration forms across different sections of the site.

No. SleekView paginates server-side and only joins the meta keys you have chosen as columns. A site with hundreds of thousands of users and dozens of meta keys still loads quickly because each page query reads only the visible page. Adding indexes on commonly filtered meta keys speeds things up further if needed.

Yes. Each subsite gets its own view, and a network admin can switch between them. User Registration installs per site in most setups, so the per-site view matches the per-site form configuration. The membership data stays scoped to the site that owns it, with no cross-site bleed.

Yes. SleekView row actions can call any registered WordPress hook. If User Registration exposes a resend-confirmation action, you can wire it to a row-level button. Selecting all pending rows and bulk-triggering the resend turns the daily onboarding nudge into a single click rather than a string of one-off emails.

Adding a new field to the form starts writing a new meta key. Add the key to the SleekView column picker and it appears alongside the existing columns. Removing a field from the form does not delete existing usermeta values, so the historical data remains visible until you decide to clean it up explicitly.