Yes. Both releases register the certificate custom post type and write a course_id post_meta on each row. SleekView reads the post type by name and the meta key by key, so the version of the add-on does not affect the chart configuration.

Yes. The ratio is calculated as certificate post count divided by completed progress count per course_id. Courses where the denominator is non-zero but the numerator is zero show as zero on the Bar, which is the clearest signal of a template misconfiguration.

Yes, when stored. Sensei Certificates writes the template post_meta on the course or globally. SleekView resolves that into a readable string on hover so the dashboard surfaces both the volume and the template used to produce each batch.

Yes. Page-level filters propagate to every card, so picking a date range, a course post_id, 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 Sensei 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 the operations team needs a quarterly issuance snapshot to send alongside the LMS completion export.

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

Yes. Each subsite has its own Sensei tables and certificate posts, and SleekView Charts reads the current subsite. Cross-site aggregation is not supported (each subsite is independent), but per-site dashboards work as expected.