Certificates
Close every training with a document that counts. Skillsive issues certificates from your own PDF template, fills the data automatically, signs them digitally and puts a verification QR code on every one — so anyone can check authenticity without an account.
A certificate in Skillsive is assembled from four things you configure once: the PDF template with your design, the fields placed on it and bound to data, the signature that appears on it, and the registry type that decides how certificates are numbered.
Once those are linked in an assignment, issuing is a click — either straight from a course completion or manually for training that happened outside VR. Every issued document lands in the registry, where it can be downloaded, verified, signed by the trainee or voided with a reason.
At a glance
- Template format
- Your own PDF, fields placed visually or mapped from PDF form fields
- Numbering
- Configurable per registry type, e.g. {Code}/{Year}/{Sequence}
- Signing key
- Platform key or your organization's own .pfx / .p12 certificate
- Verification
- Public page — scan the QR code or upload the PDF file, no account needed
- Verification results
- Valid, modified, unknown signer or not signed
How it works
Step 1: Upload your template
Start from your own PDF — the design your organization already uses — and place the data fields on it in the visual editor. The verification QR code is always there and cannot be removed.
Step 2: Set up numbering and signature
Create a registry type with your own number format, for example {Code}/{Year}/{Sequence}, and add the instructor signature with the trainer's details and stamp.
Step 3: Link it together
An assignment connects the template, the signature, the registry type, the training form and — optionally — a specific course, so the right document is used automatically.
Step 4: Issue and verify
Issue the certificate from a completed course or manually. The recipient can prove it is genuine by scanning the QR code; you can check any PDF by uploading it to the public verification page.
What you get in the panel
Visual template editor
Drag fields onto your PDF, bind each to a data source, set font size and alignment across multiple pages — and map existing PDF form fields if your template already has them.
Mandatory verification QR
Every certificate carries a QR code linking to a public verification page. You can move and resize it, but never remove it — verifiability is not optional.
Certificate numbering
Registry types define the code, name and number format, so certificates follow the numbering your internal register or a regulator expects.
Signatures
Add the instructor's signature, details and stamp, and collect the trainee's signature during issuing or later from the registry. Certificates can be finalized once the signature is in place.
Your own signing key
Sign with the platform key, or upload your organization's own .pfx or .p12 certificate so documents are signed under your organization's identity.
Registry with voiding
Search and download every issued certificate, check its verification status, void one with a reason when something changes, and use bulk actions when a whole batch is affected.
What it gives you
- Certificates issued straight from a completed VR course — no retyping
- Your own PDF design, your logo, your legally required wording
- A QR code anyone can scan to confirm authenticity in seconds, without an account
- Tamper detection: a modified file is reported as modified during verification
- Numbering that matches your internal register instead of an arbitrary sequence
- Nothing is lost — the registry keeps every certificate ready to re-download
Who it's for
Safety officers (EHS)
Hand inspectors verifiable proof of completed safety training instead of paper binders.
Training providers
Issue branded, tamper-proof certificates to client employees automatically.
HR departments
Keep every employee's training certificates in one registry, ready when needed.
Frequently asked questions
- How is a certificate verified?
- Each certificate carries a QR code linking to a public verification page. You can also upload the PDF file itself — the result tells you whether the document is valid, was modified, was signed by an unknown signer or is not signed at all.
- Can I use my own certificate design?
- Yes. You upload your own PDF and place the data fields on it in the visual editor, so the document matches your brand and any formal requirements.
- Can I number certificates the way our register requires?
- Yes. A registry type defines the code and the number format — for example {Code}/{Year}/{Sequence} — and every certificate issued under it follows that pattern.
- Can a certificate be revoked?
- Yes. A certificate can be voided in the registry with a reason recorded, and bulk voiding is available when a whole batch is affected.
- Are the certificates digitally signed?
- Yes — with the platform key by default, or with your organization's own .pfx or .p12 certificate if you upload one. Any modification of the file is detected during verification.
- What happens if an employee loses a certificate?
- Nothing is lost. All certificates live in the registry, where authorized users can find and download them again at any time.
Step-by-step guides
Detailed instructions with screenshots in the Skillsive help centre.
- Configure certificates from scratchThe recommended order for setting up certificate issuing in Skillsive.
- Create a certificate templateUpload a PDF and prepare the template used when issuing certificates.
- Set fields and QR code on a certificatePlace data fields, signatures, and the required verification QR code on a template.
- Work with the certificate registryDownload, verify, void, collect trainee signatures, and use bulk actions in the registry.
Ready to see it in action?
Tell us about your training goals and we will show you how Skillsive fits your organization — or start with a free account right away.