Myok Certificates
Classes end, the relationship continues.
A system to manage and issue digital certificates, customized for the institution itself: under your brand, on your domain, integrated with the course platform you already use and with support throughout the implementation.
This is what your graduate sees
The certificate arrives in their inbox, opens on their phone and gets shared on LinkedIn. In all three places it is the institution's brand that shows, not ours.
The certificate belongs to the institution
Full white label: the logo, colors, typefaces and seal are the institution's. It is not our template with a logo pasted on top.
Your domain
The certificate is viewed and shared from the institution itself. Whoever receives or verifies it sees the institution, not Myok.
Your programs, your wording
The title, the description, the duration and the numbering are defined course by course: completion and attendance can coexist.
Your signature
Whichever role it should carry. If the program requires it, with advanced electronic signature: FirmaGob or another accredited provider.
Your processes
The system adapts to how the institution works, and if a feature is missing, it gets developed.
From finished course to verifiable certificate
The dashed boxes are the points where the institution already has something: its course platform, or its electronic signature provider.
Moodle or another
queue, rules and mapping
signed PDF + QR
Issue the whole group at once
A full group is issued in three steps, and the system checks the data before a single email goes out.
Upload from Excel or from your LMS
Load student information straight from the course platform or from an Excel spreadsheet.
Validate before issuing
The system checks every row and shows who is ready, what data is missing and where the errors are.
Confirm once
Issuing runs in the background, the emails go out, and you can download the certificates as a ZIP and the results as an Excel file.
As automatic as the institution wants
It currently integrates with Moodle and can connect to other platforms that report when a student completes a course. Automatic issuing can coexist with spreadsheet uploads.
Triggered when the course ends
The platform can receive the data automatically when a student completes a course, with no file exports or manual handling.
Each course has its own rules
The institution defines which certificate applies, who signs it, its duration, numbering and validity.
Automatic or with approval
Each course can issue the certificate automatically or leave it pending for someone to review and approve.
We support you through the implementation
This is not an account we hand over and walk away from: it is a customization and integration service. We work with you on the branding, the connection to your systems, the pilot run and day-to-day operation.
- 1
Assessment
Your brand, your email, what the diploma says field by field and what reports you need.
- 2
Customization
We build the diploma, email and page branding together with the institution. A sample goes out for approval.
- 3
Integration
It connects to your platform and the connection is tested before anything is issued.
- 4
Pilot run
One pilot course: requests come in but nothing is issued. Each student is reviewed one by one.
- 5
Production
The first group goes out and the email, the page and the QR code are verified.
A misspelled name? Not a problem.
Student data arrives as it arrives. The system is built so an error is caught before issuing, and so an already issued certificate can be corrected without breaking what the person already shared.
Catches ID number errors
If the document number cannot belong to a person, the request stops and the system suggests a correction.
Fixes certificates already issued
If a detail is wrong, it is corrected, the diploma is regenerated and sent again. It can also be revoked.
Even if the certificate changes
The QR code the person already shared keeps working, and the changes are logged.
The certificates are public. The student database is not.
Built on Odoo and Linux, hosted on AWS: certificates are stored in S3 and published through CloudFront, on widely used and manageable infrastructure.
Personal data is not in the link
The address uses encrypted values and a random code. The student's ID number and name are not part of the shared URL.
No bulk extraction
There are no public listings or sequential addresses. Each certificate is looked up individually through its link or QR code.
On the AWS cloud
Certificates are stored and published on Amazon Web Services infrastructure.
Continuing education does not end when the course ends
The certificate keeps the institution visible after the course is over. Every time it is viewed, shared or verified, your name shows up again. And that journey can be measured.
What was issued
Certificates issued by program and period, with a record of recipient, send date and status.
What was viewed and shared
Views of each certificate and how many times it was shared, grouped by program.
Let's schedule a live demo
In 30 minutes we show you how the platform works, its main features and customization options. Then we talk about how you manage your certifications today and what your institution would need.