Primarily lifterlms_user_postmeta for per-student progress, lifterlms_quiz_attempts for quiz scores, plus the course, lesson, llms_quiz, llms_access_plan and llms_order custom post types. No data is copied, the cards render straight off the tables LifterLMS already maintains.

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

Yes. llms_order line items carry the access plan and the amount paid. Group orders by access_plan_id and sum the total, render as a horizontal bar to rank access plans by gross revenue across the period.

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 percentage, last-active date), then aggregates across the result for chart cards.

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. Direct table writes skip hooks by design for back-fills where side effects are not wanted.

Yes, where LifterLMS Pro memberships are configured. Memberships are stored as a custom post type with user enrolments in lifterlms_user_postmeta. Filter the dashboard by membership post ID and the cards show only the cohort enrolled in that membership level.

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 group-by queries use those indexes, so sites with hundreds of thousands of rows render the dashboard in well under a second on typical Kinsta or WP Engine hardware.

Yes. Any chart dashboard exports the underlying cohort or attempt log to CSV or JSON. Useful for sharing per-course reports with instructors, for combining LifterLMS data with HRIS data outside WordPress or for archival to a learner-record store.