Workplace
Corporate training certificates with an audit trail
Issue employee training and compliance certificates with expiry, SSO, SCIM, audit logs, department lists, and a public page that verifies.
On this page
Corporate training is not one cohort. Departments, locations, roles, and hire cohorts each produce a subset, and each renews on a different date. The certificate is one artefact; the list, permissions, and expiry sit behind it.
Verifycate issues employee training certificates from HR or LMS data, keeps expiry and renewal on the record, and on Pro adds SSO, SCIM, and audit logs for the workspace.
This page covers what the platform handles, what it replaces, the options for L&D, and the outcomes a compliance team can report.
What the record has to answer
| Question | What the record needs |
|---|---|
| Who completed the course? | Recipient name, employee reference, department |
| When did they complete it? | Completion date and issue date |
| Is it still valid? | Expiry date and renewal status |
| Who can see it? | Workspace role and public-page visibility |
| Who changed it? | Audit log on Pro |
What breaks in a department rollout
Compliance training is rarely one list. Departments, locations, roles, and hire cohorts each produce a subset, and each cohort renews on a different date.
The usual stack is an LMS export, a spreadsheet for the renewal dates, an email template, and a shared drive. The certificate is a PDF in that drive. When an auditor asks for evidence, someone has to reconstruct the record from three systems.
The risk is not the design. It is an expired certificate that still looks valid, or a completion record that cannot be tied back to a person.
The tools this workflow uses
| Capability | What it gives you |
|---|---|
| Certificate records | Programme, completion date, expiry, department, and employee reference as Attributes. |
| Bulk issue from HR or LMS data | Import CSV or Excel, or create recipients through the API. |
| Expiry and renewal | Set validity at issue, extend on renewal, and report status on the public page. |
| Roles and access | Workspace members and roles control who can issue, correct, or export records. |
| SSO, SCIM, and audit logs | On Pro: OIDC/SAML, directory provisioning, and a reviewable workspace activity log. |
| Correction Form | Fix a name or department on the same certificate and page without a reissue credit. |
| Custom domain and email | On Pro: certificate pages on your domain and email from your provider or SMTP. |
| Delivery analytics | Delivery, bounce, open, click, and page-view data per certificate. |
Before Verifycate
| Old approach | Friction | With Verifycate |
|---|---|---|
| LMS export plus a mail merge | A new batch every cohort; renewal dates live elsewhere | Bulk import, Attributes, and expiry on the record |
| PDFs in a shared drive | Hard to find, easy to alter, no verification | Public page with recipient, course, date, and status |
| A renewal spreadsheet | Disconnected from the certificate | Expiry date and renewal extension on the certificate |
| Email requests for name fixes | Reissue the file and resend | Correction Form on the same record |
| A manual access list | No audit trail of who changed what | Roles, SSO, SCIM, and audit logs on Pro |
How flexible it is
- Visibility. Share the public page inside the organisation, or use the certificate for internal records only.
- Expiry. Leave it off for a one-off course, or set a validity period and extend it on renewal.
- Batch shape. Issue by department, location, role, or hire cohort; one design with Attributes covers the programme.
- Delivery. Use the shared sender, or on Pro a verified domain, connected provider, or SMTP.
- Automation. Import a CSV, call the API, or trigger issuance through webhooks or Zapier.
The numbers to track
| Outcome | Where it shows up |
|---|---|
| Completion coverage by department | Recipient status and filters |
| Expired versus valid certificates | Expiry date and certificate status |
| Delivery and bounce rate | Delivery events |
| Corrections per course | Correction Requests |
| Evidence for an audit | Recipient export and audit logs |
When to use it
A single compliance course, a department programme, or a company-wide curriculum. Verifycate sits after the LMS or HR system: it does not deliver the training, but it issues and maintains the certificate record.
For a company with multiple departments, start with one cohort and one public-page policy, then extend the same Template and approval process.
For the operational steps, see how to prepare an attendee spreadsheet and how to fix certificate name errors.
Common questions
- Can we keep employee certificates private?
- Yes. Do not distribute the public link outside the organisation, or use the certificate for internal records only. Pages are noindex, but anyone with the link can open them.
- Do you support SSO, SCIM, and audit logs?
- Yes, on Pro: OIDC and SAML 2.0 SSO, SCIM provisioning, and workspace audit logs with filters and CSV export.
- How do renewals and expiry work?
- Set an expiry date at issue and extend it when the employee renews. The public page reports validity rather than disappearing when the date passes.
- Can we issue by department?
- Yes. Keep department, location, role, and course as Attributes, then issue in batches by cohort.
Related workflows
Start issuing
Issue the first batch with 300 free credits
Design once, import the list, review the recipients, and send. No card required.