Both. SleekView reads Private Areas tables and the post_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 WordPress post status update functions, which fire the same hooks the admin uses on a manual status change. Any custom listener on llms_private_area_status_changed runs exactly as if you had edited the area from the standard post edit screen.

Yes. Card layouts are per board. Your areas board can show area, scope, author, and last modified. A per cohort board can show cohort, area count, and last update. Each board remembers its own card template so the team does not reconfigure when switching context at all.

Yes. SleekView respects every WordPress capability check LifterLMS Private Areas registers. A leader who can view but not edit an area can drag a card to inspect, but the writeback only fires for leaders with the same capabilities the post edit screen would enforce on a manual save.

Add the new state in LifterLMS Private Areas the way you normally would, by adding a custom post status through the plugin filters or a custom area meta. 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 area up front. The board fetches counts via an indexed post status query, and each column loads a window of cards on demand, so even a LifterLMS site with thousands of private areas stays responsive on hosting.

Yes. Any LifterLMS related table with a status like column is a valid board. The cohort scope meta, the access rule table, and the per cohort content audit all work the same way as the main areas board does once you point SleekView at the right table to group cards on a chosen column.

It stays in sync because there is no separate database. SleekView reads the same wp_posts table the WordPress and LifterLMS Private Areas admin read. Changes on the kanban appear in the post list immediately, and edits from the admin appear on the next board refresh.