Both. SleekView reads LifterLMS Pro tables and the 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 LifterLMS enrollment functions, which fire the same hooks the admin uses on a manual status change. Any custom listener you have on llms_user_enrollment_status_changed runs exactly as if you had edited the enrollment from the standard LifterLMS admin.

Yes. Card layouts are per board. Your enrollments board can show student, course, start date, and progress. A membership board can show member, plan, and renewal date. Each board remembers its own card template so the team does not reconfigure when switching context.

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

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

No. SleekView paginates cards per column instead of loading every enrollment up front. The board fetches counts via an indexed meta query, and each column loads a window of cards on demand, so even a LifterLMS site with hundreds of thousands of enrollments stays responsive on hosting.

Yes. Any LifterLMS related table with a status like column is a valid board. The lesson progress meta, the certificate queue, and the membership table all work the same way as the main enrollments board does once you point SleekView at the right table to group on the chosen column.

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