Primarily lifterlms_user_postmeta for per-student progress, lifterlms_quiz_attempts for quiz attempts, plus the course, lesson, llms_quiz, llms_access_plan and llms_order custom post types. The plugin's tables stay the source of truth.

The core enrolment, progress and quiz columns work because the same tables back both free and Pro versions. Pro-only features (payment gateways, group buying, advanced quizzes) populate additional schema the view surfaces when present.

Yes. llms_order line items carry the access plan and the buyer. Filter the table by access_plan_id to surface every active member of a plan as a row, useful for plan-level operations.

lifterlms_user_postmeta stores per-student progress as one row per metadata key. SleekView pivots the long-format data into per-student columns (current lesson, completion percent, last-active date) so the table reads as a roster, not as a meta log.

Where SleekView writes through LifterLMS's quiz-attempt API and CRUD layer, the standard hooks fire normally so auto-grade, completion notification and certificate issuance run as expected.

Yes, where LifterLMS Pro memberships are configured. Memberships are stored as a custom post type with user enrolments in lifterlms_user_postmeta. Filter the table by membership post ID.

No. lifterlms_quiz_attempts is indexed on student_id, quiz_id and update_date, and lifterlms_user_postmeta on user_id, post_id and meta_key. SleekView's queries use those indexes, so sites with hundreds of thousands of rows render in well under a second.

Yes. Any filtered table exports to CSV or JSON with the same columns the view shows. Useful for sharing per-course reports with instructors or for combining LifterLMS data with HRIS data outside WordPress.