Yes. The add-on registers the lp_certificate post type and writes the _lp_course post_meta. Without it the LearnPress user_items table still records completions but there is no certificate post to chart. The dashboard described here depends on the add-on being active.

Yes. The ratio is calculated as lp_certificate count divided by finished wp_learnpress_user_items count per course_id. Courses where the denominator is non-zero but the numerator is zero appear as zero on the Bar, which is the clearest signal of a template misconfiguration.

Yes. LearnPress Certificates writes the template id as a post_meta on either the course or globally. SleekView resolves the template into a readable name on hover so the dashboard surfaces both volume and template per batch.

Yes. Page-level filters propagate to every card, so picking a date range, a course post_meta, or a recipient user role recomputes every Number, Pie, Bar, and Area on the dashboard. Saved views per quarter keep historical numbers stable.

Reads run against the live tables on dashboard load, so a certificate just issued by LearnPress appears immediately on the next refresh. Heavier aggregates (year-to-date issuance by template) opt into a configurable cache so they do not recompute on every visit.

Yes. Each card exports its underlying aggregated rows as CSV or JSON. Useful for compliance reports where operations need a quarterly issuance snapshot to send alongside the LearnPress completion export.

Yes. SleekView Charts reads the same lp_certificate posts the SleekView Table view writes to, so a manual issuance correction or revocation recomputes the dashboard on the next load. LearnPress hooks fire normally so downstream notifications continue to run.

Yes. Each subsite has its own LearnPress tables and certificate posts, 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.