Sensei LMS records course and lesson progress as comments with custom comment_type values (sensei_course_status, sensei_lesson_status) on the course and lesson posts, and stores quiz answers in wp_comments with related wp_commentmeta. Sensei Pro adds enrolment state in wp_sensei_lms_enrolment for membership-driven access. The default Sensei reports give per-course completion aggregates but combining enrolment, lesson progress, and quiz scores in one screen requires multiple report pages.

SleekView reads all three sources directly. A per-student progress view joins sensei_lms_enrolment with the lesson-status and course-status comments to show enrolment date, lessons completed, current lesson, and quiz averages in one row. An instructor grading queue filters quiz-answer comments where comment_approved equals zero (pending review) sorted by submission date. A cohort completion report groups students by enrolment cohort (date-range filter on sensei_lms_enrolment.created_at) and surfaces per-cohort progress.

Inline edits route through Sensei's progress APIs where supported so completion hooks fire, course-completion emails send, and any installed Sensei Pro automations (drip schedules, group leader notifications) run normally. Direct comment writes are available for back-fills where you don't want re-notifications. Multi-instructor sites get per-author scoping via the post_author on the course post.

Sensei's design choice to store lesson and course progress in wp_comments is elegant for the plugin's own logic and challenging for anyone trying to browse the data operationally. Instructors don't want to think about comment types when grading; they want a single queue of pending quiz attempts across every course they own. Program managers don't want to flip through per-course reports; they want a cohort-comparison view that says whether this term is running ahead of or behind last term.

Support reps don't want to bounce between Sensei reports, the WooCommerce side (because Sensei Pro enrolment is often payment-gated), and the user-profile screen; they want a one-row summary of a student's enrolment and progress that closes the chat ticket. SleekView's job is to read the three sources Sensei already maintains (sensei_lms_enrolment, the lesson- and course-status comments, and the quiz-answer commentmeta) and present them as the workspace those teams actually need. Sensei's own APIs handle inline edits so hooks fire and integrations stay consistent; direct writes are available for back-fills; capability gating keeps power tools out of read-only roles.