Both. SleekView reads ProfilePress tables and the account_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 ProfilePress account functions, which fire the same hooks the admin uses, including notification emails and access rule recalcs. Any custom listener you have on ppress_account_status_changed runs exactly as if you had edited the member from the standard member profile screen.

Yes. Card layouts are per board. Your members board can show email, plan, start date, and amount. An orders board can show order id, plan, amount, and refund window. Each board remembers its own card template so the team does not reconfigure when switching context.

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

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

No. SleekView paginates cards per column instead of loading every member 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 members stays responsive on standard hosting setups.

Yes. Any ProfilePress table with a status like column is a valid board. The orders table, the login attempts log, and any custom user meta tables ProfilePress adds for member fields all work the same way as the main members 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 ProfilePress meta the admin reads. Changes on the kanban appear in the members list immediately, and edits from the admin appear on the next board refresh without any cron sync.