Both. SleekView reads UserPro tables and the userpro_status column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.

SleekView calls the UserPro account functions, which fire the same hooks the admin uses, including welcome emails. Any custom listener you have on userpro_status_changed runs exactly as if you had moderated the user from the standard UserPro profile screen yourself.

Yes. Card layouts are per board. Your verification board can show email, role, and registration date. A messages board can show sender, recipient, and report status. Each board remembers its own card template so the team does not reconfigure when switching context.

Yes. SleekView respects every WordPress capability check UserPro registers. A user who can view but not edit other users can drag a card to inspect, but the writeback only fires for users with the same capabilities the user edit screen would enforce on a manual save.

Add the value in UserPro the way you normally would, by adding a new verification state through the plugin filters or a custom user meta key. SleekView picks it up on the next board load because columns are derived from the distinct meta values present on rows, not a hard coded list.

No. SleekView paginates cards per column instead of loading every user up front. The board fetches counts via an indexed meta query, and each column loads a window of cards on demand, so even a site with hundreds of thousands of users stays responsive on standard hosting setups.

Yes. Any UserPro related table with a status like column is a valid board. The messages table grouped by report state, the friends table grouped by request state, and the activity log all work the same way as the main verification board does on the WordPress users surface.

It stays in sync because there is no separate database. SleekView reads the same wp_users table and the UserPro meta the admin reads. Changes on the kanban appear in the user list immediately, and edits from the admin appear on the next board refresh without sync.