Yes. SleekView normalises the good_lms_students post_meta value (a serialised array of user_ids) into individual rows at read time, so chart cards aggregate cleanly without per-render PHP unserialisation. The normalisation is cached and refreshes when the source meta changes.

Yes. Page-level filters propagate to every card, so picking a course post_id, an instructor post_author, or a date range recomputes every Number, Pie, Bar, and Area on the dashboard.

Yes. Quiz scores live in good_lms_quiz_score_{quiz_id} user_meta keys. SleekView reads them and a Bar grouped by quiz_id with Average on score surfaces difficulty across the catalogue. A Pie can also show pass-rate share if the plugin writes a pass meta value.

Good LMS is a CodeCanyon plugin and updates are intermittent. SleekView Charts reads stock post_meta and user_meta keys, so the dashboard does not depend on plugin updates. As long as the keys remain the same (which is the case across all current versions), the charts work.

Reads run against the live meta tables on dashboard load, so a student progress write appears on the next refresh. Heavier aggregates (lifetime completion counts across the catalogue) opt into a configurable cache so they do not recompute every visit.

Yes. Each card exports its underlying aggregated rows as CSV or JSON. Useful for academy reviews that need a snapshot of completion counts and quiz averages alongside any external HRIS data.

Yes. SleekView Charts reads the same meta rows the SleekView Table view writes to, so a manual progress reset or quiz score correction recomputes the dashboard. Good LMS hooks fire normally so any downstream completion notifications continue to run.

Yes. Each subsite has its own Good LMS courses and meta, 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 on each subsite.