Both. SleekView reads Theme My Login tables and the tml_moderation_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 Theme My Login moderation functions, which fire the same hooks the admin uses, including notification emails. Any custom listener you have on tml_moderate_user runs exactly as if you had moderated the user from the standard user profile edit screen yourself.

Yes. Card layouts are per board. Your moderation board can show email, role, and registration date. A login history board can show user, login result, and last attempt. Each board remembers its own card template so the team does not reconfigure when switching context.

Yes. SleekView respects every WordPress capability check Theme My Login 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 Theme My Login the way you normally would, by adding a new moderation state through the plugin filters or by adding 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.

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 Theme My Login related table with a status like column is a valid board. The login history table can be visualized too, grouped by login result so admins can audit failed login attempts and suspicious patterns alongside the moderation queue board.

It stays in sync because there is no separate database. SleekView reads the same wp_users table and the Theme My Login 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.