No. SleekView reads the WP Community member meta and group tables in place and renders columns from the live data. There is no separate sync step and no second store to keep in line, so the board always matches what you would see in the plugin admin.

Yes. SleekView writes status changes through the WP Community API rather than editing rows directly, so any hook the plugin fires for approvals, suspensions, or group access still runs exactly as it would after a manual change in the standard plugin admin.

Yes. Each board has a filter layer that runs before the columns are built, so you can scope it to a specific group, a role, a recent signup window, or any combination of those. Site-wide moderators usually keep a broader board while group leads use scoped ones.

You pick any field on the user record, the linked group membership, or the moderation log. Common picks are display name, primary group, role, report count, signup date, and last activity. Role and group names render as chips so the card scans quickly.

It runs alongside. The kanban is an alternative view of the same member records, so anything you change on the board shows up in the plugin admin on the next load and anything you change in the admin shows up on the board the same way.

Yes. SleekView respects WordPress capabilities, so you can grant a moderation role that lets them work the board for their groups while keeping them out of unrelated site settings. Read-only boards are available for community stakeholders who only need visibility.

Each column loads with its own pagination rather than fetching every member at once, and the filter layer pushes work to the database. Large communities stay fast, and you can archive old groups so the board reflects current activity instead of years of history.

It complements them. Static reports and CSV exports still answer batch questions about totals and trends, while the kanban is the live surface where moderators move accounts through the lifecycle without bouncing between admin screens and exports.