Sensei LMS is unusual because it stores course progress and quiz answers in the WordPress wp_comments table, using comment types like sensei_course_status, sensei_lesson_status, and sensei_user_answer. The comment_approved field carries the progress state, with values such as in-progress, complete, failed, and passed. The Sensei admin shows a Students screen, but it does not visualize cohorts as cards in columns matching each progress state.

SleekView Kanban filters wp_comments to the Sensei comment types and joins them against the parent course or quiz post and the learner user. The natural column to group by is the comment_approved field, which gives you Not Started, In Progress, Completed, and Failed stages out of the box. Card fronts show learner name, course title, current lesson, percent complete, last quiz score, and the comment_date so you can see exactly when a learner stalled.

Drag a card from In Progress to Completed and SleekView calls Sensei's progress update functions so completion emails, certificates from Sensei Pro, and any hooks you have wired keep firing. Failed quiz attempts and abandoned learners stay in their own columns, which keeps the data you need for retake outreach visible.

Sensei stores progress as comments which is elegant from a developer point of view but unfriendly from an instructor point of view. The default Learners screen prints a paginated table. Each row is a learner with a course and a status, but the table cannot answer questions like which fifteen learners enrolled last week and never opened a lesson.

That question is the moment you can save a learner before they leave. A kanban view answers it instantly because the Not Started column visually shows you those fifteen cards with their enrollment date and no last-activity timestamp. The board collapses ten minutes of comment-table filtering into one glance.

The drag-to-update piece matters too. Marking a learner complete or recording a quiz retake used to require finding the right comment row, editing the approved value, and trusting that no Sensei hook expected the update to come through a helper function. With the kanban the update runs through Sensei's official progress functions, so emails and Sensei Pro certificates fire correctly every time.