Certificates
How a certificate is earned, where it lives, and how somebody who does not have a Hue Eval account can check that it is real.
Practice tests measure you. Certification tests credential you — clear one above its pass mark and Hue Eval issues a certificate with your name on it and a link that anybody can verify.
Earning a certificate
Certification tests live on their own page, separate from practice, and are grouped by the course they belong to. Each test states its own rules before you start:
The percentage you have to clear. Set per test — it is not a platform-wide number.
How many tries you get, where the test limits them. Some are unlimited.
A time limit, where the test sets one.
Some certifications are locked. A locked one does not appear in your list at all until you enter its code — see below.
Finish above the pass mark and the certificate is issued immediately. There is no review queue and nothing to wait for.
Passcodes
An organization can put a passcode on a certification so that only the people it gave the code to can see it. If you were given one, enter it in the certification passcode box on the certification tests page and that certification appears in your list.
Each code opens exactly one certification. Codes are not case-sensitive, so it does not matter how you type it.
Your certificate page
Everything you have earned sits on your certifications page — your shelf. Each certificate shows the test, the organization that issued it, your score, and the date. From there you can:
- Download it as a file to attach to an application.
- Create a public link, which turns it into a page anybody can open.
- Share it, with the message already written for the network you are posting to.
A certificate has no public link until you create one. Before that it is visible only to you and to the organization that issued it.
Sharing it
The public page is built to be posted. It carries the certificate, the issuing organization, the award statement and the date, and it renders a preview card when the link is pasted into LinkedIn, a message or a chat — so what people see is the certificate, not a bare URL.
LinkedIn gets the primary button, with a composed post rather than just a link. Because LinkedIn fetches the preview from the page itself, the dialog also offers the certificate image to save, so you can attach it directly if you would rather post an image than a link.
Verification
The public certificate page is the verification. Anyone with the link — a recruiter, an admissions office, a client — can open it without an account and see the certificate as issued, together with the organization that issued it and when.
The page is also marked up as a credential for machines that read pages that way, so a verification service or a profile importer can read the issuer, the recipient and the date without a human in the loop.
Nothing on a certificate page is editable after issue. If a detail is wrong, the organization reissues it rather than amending it in place — which is what makes the link worth trusting.
Certificates for tests sat offline
An organization can run a test in a room, on paper, and still issue the certificate here. The certification is published as an attestation: candidates sign in, enter the passcode they were given, confirm their name, and the certificate for that cohort is issued to them.
The certificate says what it is — a certificate of participation in the programme named on it, dated to the cohort's completion date. It is the same shareable, verifiable page as any other, because the record of who completed what is the same record either way.