EduAdmin Integration
EduAdmin course participants can receive TRUE certificates automatically
EduAdmin already holds your course occasions, your participants and who attended. TRUE connects to it through EduAdmin's own open API, so when a course is finished the participants receive a branded, blockchain secured certificate on your own domain. The connection is built and running, and we configure it against your account with you.
TL;DR
EduAdmin publishes an open API, using the OData standard with OAuth for access, that covers participant lists and course status. That is everything a certificate needs. We set the connection up against your EduAdmin account, agree which course types should issue and what the certificate should say, and from then on participants receive their certificate without an administrator exporting anything. The credential carries your design, sits on your own domain, and is written to blockchain at the moment of issue.
- Already connected. This is a connection we run, not a project you have to scope.
- Uses EduAdmin's own API. Access is granted through OAuth on your account, so you can see it and withdraw it.
- You choose what issues. Not every course occasion in EduAdmin deserves a certificate, and you decide which do.
How does the EduAdmin certificate integration work?
EduAdmin is where your course administration already lives: occasions, bookings, participants, attendance. TRUE reads what it needs from EduAdmin's own API and issues from there. The point is that your administrators keep working in EduAdmin exactly as they do today.
1
Grant access on your EduAdmin account
EduAdmin uses OAuth, so access is issued from your side and can be withdrawn there. We do this step together with you.
2
Agree which courses issue
Not every occasion in EduAdmin should produce a certificate. We go through your course types with you once and set the rule.
3
Certificates issue themselves
When a course is completed, each participant receives a branded, blockchain secured certificate with a permanent verification link. Nobody exports a list.
What does the certificate carry?
The participant name, the course, your organisation and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Participant name and course. Read from EduAdmin itself, so it matches your course administration 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 EduAdmin account, a decision about which courses issue, and a certificate design. The access is one OAuth step, and the design is the only part that takes any real decision making.
- Access to your EduAdmin account, granted through OAuth from your side.
- The course types that should issue, agreed once so nothing starts issuing before you mean it to.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a participant 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 participant data handled?
We read the participant name, email address and the course details, which is what a certificate needs to exist. Access is granted through OAuth on your EduAdmin account, so you can see what has been granted and withdraw it in the same place.
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 EduAdmin attendance record on its own enough?
It proves the participant attended, which is enough for your own administration and your invoicing. What it cannot do is prove anything to an employer who was not there.
| Capability | The attendance 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 |
| Who has to do the work | Somebody exports and sends | Nobody, it issues on completion |
| Analytics | None | Views, shares and verifications tracked |
What do EduAdmin users ask about this?
Mostly whether they have to change how they work, who grants access and whether every course is affected. No, you do, and only the ones you choose.
Do our administrators have to work differently?
No. They keep working in EduAdmin exactly as they do today. The certificate is issued from what EduAdmin already records.
Who grants the access?
You do. EduAdmin uses OAuth, so the access is issued on your account and can be withdrawn there whenever you want.
Does every course issue a certificate?
Only the course types you choose. We agree the rule with you once, and a course that should not produce a certificate never does.
What about a participant who booked but did not attend?
They do not receive a certificate. The rule follows your own attendance record, which is the point of reading it from EduAdmin rather than from a booking list.
Do participants 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 courses that already finished?
Yes. Earlier completions 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 certificate design, set the connection up against your EduAdmin account with you, and the next completed course issues on its own.