Yes. The free toolkit and the paid pro bundle register modules through the same hook, and SleekView reads that registry directly. The kanban renders the same way regardless of which combination of free and pro modules your LMS has installed, which means upgrading does not break the board.

Yes. The drag handler calls the same Uncanny activation hook the toolkit admin toggle uses, which triggers any LearnDash cache flush, shortcode registration, or settings page registration the module relies on. Drag activation produces exactly the same downstream effect as toggling each module row.

Yes. SleekView only flips the active flag, so any module-specific settings stored in wp_options stay intact when a card moves from enabled back to disabled. Dragging the card forward again later restores the same module configuration without forcing the LMS lead to reconfigure settings.

Yes. SleekView views are configuration only, so you can build one board filtered to the courses category and another to the users category from the same module registry. Each admin picks a default board, and lead admins pin shared boards into the sidebar for the whole LMS team.

SleekView reads the module registry on every page load, so a new category shows up automatically inside the filter bar with a fresh count. No board reconfiguration is needed, and you can immediately filter the active lanes to that new category to see which modules in it are ready.

Each module card opens a side panel listing the module description, the version number, the minimum LearnDash version it requires, and any related modules it depends on. LMS leads plan a rollout by reading those dependency notes directly inside the kanban side panel rather than the toolkit admin.

Yes. SleekView respects WordPress capabilities, so you can require an LMS admin capability before a card lands in the beta or enabled lane. Curriculum staff can plan in the disabled lane and request a move, but only the LMS lead can actually move a card forward through the activation flow.

SleekView reads and writes the existing toolkit registry in wp_options without adding shadow tables for module activation state. View configuration sits in its own small options row, so uninstalling SleekView leaves every module flag and setting exactly where Uncanny Toolkit wrote it.