Every certificate gets a public page
Each issued certificate has a public page with the recipient, award, issuer, date, and verification details — no login required.
A PDF attached to an email is a file, not a record. It can be renamed, cropped, or edited, and a viewer has no easy way to check whether it came from the organisation it claims.
Every issued certificate has a public page.
What the page contains
The recipient's name, the award or event, the issuer, the issue date, and any expiry date. It also carries the certificate details — type, duration, skills, earning criteria, and a learn-more link when configured — plus the verification controls.
The page opens from the certificate email, a shared link, or the QR code. The recipient does not need an account; the viewer does not need one either.
Why a page instead of a file
A public page can be updated without resending a file. A correction to a name updates the same URL. An expired certificate can say it is expired instead of disappearing. A verifier can open the page and see the evidence rather than trusting the screenshot.
What to share
The public page carries recipient-identifying data by design. Share the link deliberately. Certificate pages are not meant to be indexed by search engines; the page is reachable by link, QR code, or certificate ID, not by searching a recipient's name.
The public page is the canonical record. A downloaded PNG or PDF is a copy of the certificate, not a replacement for the page.
Related