Content health

Content health brings together three screens that help you track a certified content over time: a per-content view on the administrative dashboard, a block of actions on the content version itself, and the e-mail reminder those actions trigger for enrolled participants.

Dashboard view: Content Health

On the administrative dashboard, the Content Health tab (Certificates group in the side menu) shows one row per content with at least one enrollment. Each row shows the Content, how many Classes it has, its total enrollments (#Enr) and issued certificates (#Cert), and three tracking columns:

Expires 90 days - certificates that expire within the next 90 days (the same window as the expiring-certificates listing) and their share of the issued certificates; above 30% is highlighted.
Replaced: no certificate on the successor - for a content replaced by a newer version, how many holders of its certificate still have no certificate on the direct successor, counted from enrollments (one hop only). A dash means the content was not replaced.
Activity - Active when some enrollment was touched in the last 365 days, Dormant (highlighted) when none was, and Never active when no enrollment was ever opened (highlighted when the enrollments themselves are older than 365 days). The date shown is the last activity.

Highlighted rows - for more than 30% of certificates expiring within 90 days, for Dormant content or for Never active with old enrollments - come first in the list, and clicking any row opens the matching content.

Block on the content version: reminder and history

When editing an already saved content version, the Configuration tab gains a Content health section with two buttons side by side.

Remind enrolled participants e-mails every participant enrolled in this content’s classes, asking them to complete the current version. Clicking it shows a confirmation with how many people would be notified right now - for example, “Send an e-mail reminder about this content to its 42 enrolled participant(s)? Participants who opted out of platform e-mails are skipped.” Once confirmed, the send happens in the background and the button stays disabled for the rest of the day: only one reminder per version per day is allowed.

The Last reminder field, next to the buttons (it only shows up after the first send), reports progress:

“Reminder being sent since HH:MM - N recipient(s)” while today’s send is still in progress;
“Reminder sent today at HH:MM (N sent, M not contacted)” when the send finishes the same day;
“Reminder sent on <date> (N sent, M not contacted)” for a send from an earlier day;
if a send has failures, the field says how many failed and that failed sends are retried automatically.

When a send finishes, an on-screen notice summarizes the outcome: “Reminder sent: N sent, M without e-mail, P without consent, Q failed.”

Export version history downloads a spreadsheet (XLSX) with this version’s history: lineage, replacements, validity terms, and counts per version. The spreadsheet carries no participant data.

The e-mail reminder

The e-mail a participant receives asks them to complete the current version of the content. Like every automatic reminder on Eduvem, participants who opted out of platform e-mails are never contacted.

Common questions

Why don’t I see the Content Health tab on the dashboard, or the block on the content version? Certificate validity is not enabled for your institution, or you do not have the institution administrator role - the block on the content version requires that role, and the dashboard tab follows the same access rules as the rest of the administrative dashboard.

Can I send the reminder more than once on the same day? No. It is one reminder per version per day; the button becomes available again the next day.

Does the history export include participant names? No. It is an aggregate spreadsheet, with lineage, replacements, validity terms and counts per version - no participant data.

What does a dash mean in the replaced-version column? That the content was not replaced by any successor version.