Both. SleekView reads LearnDash BuddyBoss tables and the is_banned 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 BuddyBoss group membership and LearnDash BuddyBoss sync functions, which fire the same hooks the admin uses on a manual membership change. Any custom listener on ld_buddyboss_group_access_changed runs as if you had edited the group from the standard admin.

Yes. Card layouts are per board. Your memberships board can show learner, group, role, and progress. A per course progress board can show learner, course, completion, and last activity. Each board remembers its own card template so the team does not reconfigure when switching.

Yes. SleekView respects every WordPress capability check BuddyBoss and LearnDash register. A leader who can view but not edit a group can drag a card to inspect, but the writeback only fires for leaders with the same capabilities the BuddyBoss admin would enforce on a manual save.

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

No. SleekView paginates cards per column instead of loading every membership up front. The board fetches counts via an indexed status query, and each column loads a window of cards on demand, so even a BuddyBoss community with hundreds of thousands of memberships stays responsive.

Yes. Any BuddyBoss or LearnDash related table with a status like column is a valid board. The activity stream, the friend requests table, and the per course progress summary all work the same way as the main memberships board once you point SleekView at the right table to group on.

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