No. SleekView Charts reads learndash_user_activity, learndash_user_activity_meta and the learndash_pro_quiz_* tables directly, so the course and quiz dashboards described here work without ProPanel. ProPanel adds its own visualisation; the two can coexist if you want both, but neither requires the other.

Yes. learndash_pro_quiz_statistic_ref stores per-question answers per attempt. Group by question_id with a Pie or Bar split on correct vs incorrect to see which questions are tripping the cohort. Useful for instructional designers iterating on quiz content based on real student responses.

Yes. Filter learndash_user_activity by the user IDs that belong to a LearnDash group, then group by activity_status for a cohort progress pie. The same pattern works for any user subset (active subscribers in a membership plugin, alumni, beta testers).

Where SleekView writes through LearnDash's APIs (course completion, lesson completion, quiz grading), the standard hooks fire normally, so certificates issue, notifications send and group progress recalculates. Direct table edits skip hooks by design for back-fills where side effects are not wanted.

The cards render straight off the live LearnDash tables, so the data is as fresh as the activity rows LearnDash has already written. There is no scheduled aggregation job and no separate analytics store to wait on, the dashboard reflects the state of learndash_user_activity at request time.

No. learndash_user_activity is indexed on user_id, activity_type, activity_status and activity_started, and SleekView's group-by queries use those indexes. Sites with millions of activity rows render the dashboard in well under a second on typical Kinsta or WP Engine hardware.

Yes. Any chart dashboard exports the underlying filtered cohort to CSV or JSON. Useful for combining LearnDash data with HRIS data outside WordPress, for sharing a course review with a programme sponsor or for archival to a learner-record store.

Yes. SleekView Charts and the SleekView table view operate on the same dataset. Apply a filter on the chart and the underlying activity table reflects the same scope. The team flips between the dashboard for the overview and the table for the row-level intervention without rewriting filters.