No. SleekView reads learndash_user_activity and the pro_quiz_* tables directly. ProPanel adds its widget visualisations; the two can coexist if you want both, but neither requires the other.

Yes. learndash_pro_quiz_statistic stores per-attempt scores. Filter to attempts below pass threshold and group by user or by quiz to surface the friction points across the catalogue.

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.

Yes. Filter activity rows by the user IDs that belong to a LearnDash group, then save the view. Each cohort gets its own table without rewriting filters every Monday.

The table renders straight off the live 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.

No. learndash_user_activity is indexed on user_id, activity_type, activity_status and activity_started, and SleekView uses those indexes. Sites with millions of rows render in well under a second on typical Kinsta or WP Engine hardware.

Yes. Each saved view captures column set, filters and sort order, gated by WordPress capability. Course managers see operations; governance sees compliance; instructors see their courses.

Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for compliance reporting or for combining LearnDash data with HRIS data outside WordPress.