Horbit Docs

Certificates

Designed templates, serialised issuance, PDF delivery and verification.

Certificates turn attendance or achievement into a document the recipient can keep and a third party can check. A template is designed once, then issued in batches against an event's attendees.

Certificate templates
Templates are designed in the console and reused across issuances.

How it fits together

  1. A template — the visual design, with placeholders for the recipient's name, the event, the date and the serial.
  2. An issuance — one batch, usually tied to an event. It records who was included and when it ran.
  3. A certificate — one row per recipient, carrying a serial number unique within the tenant, a snapshot of the recipient's name and email at the time of issue, and a PDF.

The snapshot matters: a certificate issued in March still reads correctly after the recipient changes their name or email in June. The document is a record of what was true when it was awarded.

Use cases

Certifying a training cohort

Run an issuance against the event's attendance list. Everyone who actually checked in gets a serialised certificate; nobody has to be typed in.

Verifying one later

Serials are unique per tenant and resolvable, so an employer holding a PDF can confirm it was really issued rather than trusting the artwork.

Starting from a ready-made design

The platform keeps a store of certificate templates a tenant can adopt and re-brand, rather than starting from an empty canvas.

On this page