Both. SleekView reads LearnDash Groups tables and the learndash_group_users 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 LearnDash Groups membership functions, which fire the same hooks the admin uses on a manual membership change. Any custom listener you have on learndash_update_group_access runs exactly as if you had edited the group from the standard LearnDash 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 LearnDash registers. 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 LearnDash group edit screen would enforce on a manual save.

Add the new state in LearnDash the way you normally would, by adding a custom membership state through the plugin filters or a custom user meta key. SleekView picks it up on the next board load because columns are derived from the distinct values present 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 meta query, and each column loads a window of cards on demand, so even a LearnDash site with hundreds of thousands of memberships stays responsive.

Yes. Any LearnDash related table with a status like column is a valid board. The course progress meta, the group reporting table, and the cohort summary all work the same way as the main memberships board once you point SleekView at the right table and pick a column to group on.

It stays in sync because there is no separate database. SleekView reads the same group meta the LearnDash Groups admin reads. Changes on the kanban appear in the group user list immediately, and edits from the admin appear on the next board refresh without cron sync.