Simployer Integration
Simployer can issue TRUE certificates when an employee earns one
Simployer is where your people data lives, including the training and the certifications you record against them. TRUE connects to it so an employee who earns something receives a real credential rather than a line in a system they cannot show anyone. It carries your design, sits on your own domain, and is written to blockchain at the moment of issue.
TL;DR
Simployer publishes a developer programme with an HRConnect API covering core HR data, people and organisational structure. That is the route TRUE uses. We agree with you which HR event means a credential has been earned, whether that is an internal training marked complete, a certification registered, or a role requirement met, and set the connection up against your Simployer account. Because Simployer is an HR system rather than a learning platform, the definition of earned is a decision worth making deliberately, and we make it with you.
- Built on Simployer's own API. The HRConnect API is a documented part of Simployer's developer programme.
- The trigger is yours to define. An HR system records many things; only some of them deserve a credential.
- Employees get something they can use. A credential they can show outside the company, not a record only HR can see.
How does the Simployer certificate integration work?
Simployer already holds the person and the thing they earned. TRUE reads what it needs and issues from there, so HR keeps working in Simployer and the employee ends up with a credential they can actually show somebody.
1
Decide what earned means
This is the real decision, and it is yours. An HR system records a lot; a credential should mark something worth proving. We work through it with you.
2
Connect to your Simployer account
We set the connection up against your account, using Simployer's own API programme. We confirm the exact route against your setup rather than assuming it, because Simployer configurations differ.
3
Credentials issue themselves
When the event you defined happens, the employee receives a branded, blockchain secured credential with a permanent verification link.
What does the credential carry?
The employee name, what they earned, your organisation and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Employee name and credential. Read from Simployer itself, so it matches your HR record rather than a copy of it.
- Your organisation. The certificate is branded as yours and lives on your own domain.
- Date of issue, fixed. Written to blockchain at issuance, which is what makes backdating impossible.
- A permanent verification link. An employer confirms it by opening the link or scanning the QR code, without contacting you.
What has to be in place before it can be switched on?
Access to your Simployer account, a clear definition of the event that means earned, and a credential design. The definition is the part worth spending time on.
- Simployer administrator access, so the connection can be set up against your account.
- The HR event that means earned, defined clearly. This is the difference between a credential that means something and one that does not.
- A credential design, built by us to your profile or adapted by you from an existing template.
What does an employee receive?
A branded, animated certificate delivered by email, on your own domain rather than ours. It carries a QR code and a permanent verification URL, so anyone can confirm it without contacting you, and it goes onto a LinkedIn profile in one click.
- Beautifully designed. Animated, branded and interactive rather than a static PDF.
- A shareable link. One URL that works in an email signature, a portfolio or a CV.
- QR code verification. An employer, a client or a regulator confirms the credential instantly.
- LinkedIn ready. Added to a profile in one click, which puts your name in front of their network.
- Blockchain secured. It cannot be edited, forged or backdated after issue.
How is employee data handled?
We use the employee name, work email address and what they earned, which is what a credential needs to exist. An HR system holds a great deal more than that, and none of the rest is needed or used.
TRUE is hosted in the EU, and we sign a data processing agreement with you before anything is switched on.
How much has TRUE issued for organisations like yours?
More than 500,000 documents for over 200 organisations in 15 or more countries, and credentials shared by their recipients have produced over 100 million marketing impressions. These are TRUE platform figures, not third party research.
500K+ Documents issued
200+ Organisations
15+ Countries
100M+ Marketing impressions
Is an HR record on its own enough?
It proves the training happened, which is enough for your own compliance reporting. What it cannot do is travel with the employee, and that is often the whole point of the training.
| Capability | The HR record on its own | The record with TRUE connected |
|---|---|---|
| Proof outside your organisation | The reader has to take it on trust | A permanent verification link anyone can open |
| Tamper proof | No | Yes, written to blockchain at issue |
| Lives on your domain | No | Yes, branded on your own domain |
| LinkedIn shareable | A file to attach | One click add to LinkedIn |
| Effort per participant | Manual handling for anything formal | None, it issues on completion |
| If the employee leaves | The proof stays behind in your HR system | The credential stays with the person |
| Analytics | None | Views, shares and verifications tracked |
What do HR teams ask about this?
Mostly what should count as earned, what data leaves the HR system and what happens when somebody leaves. You decide, only what a credential needs, and the credential stays with them.
What should trigger a credential?
Something worth proving to somebody outside the company: an internal training completed, a certification registered, a role requirement met. We work through it with you, because an HR system records a great deal that should not become a credential.
What data leaves Simployer?
The employee name, work email address and what they earned. Nothing else, because nothing else is needed to make a credential.
What happens if an employee leaves?
The credential stays with them. That is the point of it: they earned the training, and it should not disappear from their record because they changed jobs.
Does this work with how our Simployer is set up?
We confirm that against your account rather than assuming it. Simployer configurations differ, so the exact route is something we check before we promise a date.
Do recipients need a TRUE account?
No. The certificate arrives by email with a unique link. No login, no account and no app.
Can the certificate carry our own design?
Yes. We build the design to your graphic profile, or you adapt one from an existing template. The certificate is branded as yours and lives on your own domain.
Can we issue certificates for records that already closed?
Yes. Earlier records can be issued as a batch, so a backlog does not have to be handled by hand.
What does a recipient do with the certificate?
Share it. It is a link rather than a file, so it goes on a LinkedIn profile in one click and into an email signature or CV, and every share points back to a verification page carrying your name.
Ready to switch it on?
We prepare your credential design, define the trigger with you and confirm the route against your Simployer account, and the next employee who earns one receives it.