Both. SleekView reads Profile Builder tables and the wppb_approval_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 Profile Builder approval functions, which fire the same hooks the admin uses, including notification emails. Any custom listener you have on wppb_approve_user or wppb_unapprove_user runs exactly as if you had approved the user from the standard user profile edit screen.

Yes. Card layouts are per board. Your approval board can show email, role, and registered date. A role audit board can show display name, last login, and capability set. Each board remembers its own card template so the team does not reconfigure when switching contexts at all.

Yes. SleekView respects every WordPress capability check Profile Builder 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 Profile Builder the way you normally would, by setting a new approval state in the plugin filters or a custom user meta. SleekView picks it up on the next board load because columns are derived from the distinct meta values present, not from a hard coded enum.

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 registered users stays responsive on standard hosting.

Yes. Any user-related table with a status like column is a valid board. The login attempts log, the password reset token table, and custom user meta tables Profile Builder adds for member fields all work the same way as the main approval queue does on the main users board.

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