Moodle Integration
Moodle course completions can issue TRUE certificates
Moodle already records the moment a course is completed. It just does not, on its own, tell anybody else about it. That gap is the whole job here, and it is a small one: our team connects TRUE to your Moodle so a completion issues a branded, blockchain secured certificate on your own domain, and nobody exports a list.
TL;DR
Moodle has an events system that includes course completion, and it has web services for reading data out. What a standard Moodle install does not have is an outgoing webhook, so the connection is made in one of two ways. Either a webhook plugin is added to your Moodle and pointed at TRUE, or TRUE reads completions through Moodle's web services on a schedule. Both are ordinary work our team does with you, and both end the same way: the learner gets a certificate that anybody can verify.
- The TRUE side is built. Issuing, the design, the verification page and the blockchain record are all in production. The work is the connection.
- Two routes. A webhook plugin on your Moodle, or TRUE reading completions through Moodle's web services. We pick with you.
- Your Moodle stays yours. Nothing is changed in how your courses are built.
How does the Moodle certificate integration work?
Moodle knows when a course is completed, because completion is one of the events it records. The question is only how that reaches us. Once it does, everything after it is the same for Moodle as for any other platform: the certificate is issued against your design and delivered to the learner.
1
We look at your Moodle with you
Which version, which plugins, who administers it. Moodle installations differ more than most platforms, so this is a real step rather than a formality.
2
Choose the route
Either a webhook plugin on your Moodle, pointed at TRUE when a course is completed, or TRUE reading completions through Moodle's web services on a schedule. Which is better depends on your install.
3
Certificates issue themselves
Once it is running, a completion produces a branded, blockchain secured certificate with a permanent verification link. Nobody has to trigger it.
What does the certificate carry?
The learner 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.
- Learner name and course. Read from the Moodle completion itself, so it matches your course 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?
Someone who administers your Moodle, agreement on the route, and a certificate design. Because you host your own Moodle, the person who maintains it has to be part of the conversation.
- Access to your Moodle administrator, or to whoever hosts it for you.
- A decision on the route, plugin or web services, which we make with you once we have seen your install.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a learner 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 learner data handled?
The connection passes the learner name, email address and the course details, which is what a certificate needs to exist. Because your Moodle is yours, the access we are given is scoped by you and can be withdrawn by you.
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 a Moodle completion on its own enough?
It proves the course was completed inside your Moodle, which is enough internally. What it cannot do is prove anything to somebody who has no login, and that is the part the connection adds.
| Capability | Completion on its own | Completion 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 learner | Manual handling for anything formal | None once the connection is running |
| Setup | Not applicable | One short piece of work with your Moodle administrator |
| Analytics | None | Views, shares and verifications tracked |
What do Moodle administrators ask about this?
Mostly whether a plugin is required, whether it changes their courses and how long it takes. Not always, no, and it is short.
Do we have to install a plugin?
Not necessarily. A webhook plugin is one route and it is usually the tidier one. The other is TRUE reading completions through Moodle's own web services, which needs nothing added to your install. We recommend one after seeing your setup.
Does anything change in how we build courses?
No. Course completion is already something Moodle tracks. We use it rather than asking you to work differently.
Which Moodle version do we need?
We check that against your install rather than quoting a number. Moodle installations differ a great deal, which is exactly why we look before we promise.
Who does the work?
We do, together with whoever administers your Moodle. It is a short piece of work, not a project.
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 look at your Moodle?
Show us your install and we will tell you which of the two routes fits, what it takes and how quickly the first certificate can go out.