Both work. The schema is identical (wp_stm_lms_user_courses, wp_stm_lms_user_lessons, wp_stm_lms_quizzes) and Pro adds payment-related rows but does not change the join keys. SleekView Charts reads the same source on either tier, so a free MasterStudy site can build most of the dashboard described here.

Yes. SleekView dashboards support page-level filters (course, instructor, date range, status) that propagate to every chart card. Pick an instructor and the Number, Pie, Bar, and Area cards all recompute against that subset.

Yes, when stored. MasterStudy Pro writes commission rows linked through course post meta. SleekView joins through that key so a Bar card can rank instructors by commission earned alongside enrolment count, on the same dashboard.

Yes. wp_stm_lms_quizzes stores attempts with passed and score columns. A Pie card on passed gives the pass-rate share, and a Bar grouped by course_id with Average on score surfaces courses where quiz performance is collapsing.

Reads run against the live tables on dashboard load, so the numbers reflect activity up to that moment. Heavier aggregates (lifetime instructor revenue) opt into a configurable cache so they do not recompute on every visit; the cache window is per-card.

Yes. Each card exports its underlying aggregated rows as CSV or JSON. Useful for marketplace operations where finance needs a quarterly instructor commission snapshot alongside the WordPress order export.

Yes. SleekView Charts reads the same wp_stm_lms tables the SleekView Table view writes to, so a status change or progress correction recomputes the dashboard on the next load. MasterStudy hooks fire normally so downstream certificates and notifications continue to run.

Yes. Each subsite has its own MasterStudy tables and SleekView Charts reads the current subsite. Cross-site aggregation is not supported, but per-site dashboards behave as expected and can be scoped per role.