Public credential verification lets a third party check the current provider-attributed record instead of trusting only a screenshot or static document.
The three parties
A credential involves an issuer, a holder and a verifier. The issuer makes the claim, the holder receives it, and the verifier checks it for a particular purpose.
Enrolius serves the issuer's verification record. It does not decide whether an employer, regulator or accreditor must accept the credential.
Why a live result matters
A PDF can be copied, edited or viewed after the underlying credential has expired. A live verification result can show the current status, issue and expiry dates, issuer and credential name. It can also reflect revocation or correction according to provider policy.
Use an opaque reference
Verification links should not expose sequential database IDs that allow someone to enumerate records. Enrolius uses opaque tokens for public verification. A token is difficult to guess, but providers must still minimize the information displayed.
What a verifier should see
The page should answer:
- Who issued the credential?
- What credential was issued?
- To whom, using the minimum appropriate identity?
- When was it issued?
- Is it current, expired or otherwise not active?
- What program or criteria does the issuer associate with it?
Underlying evidence, private notes and unnecessary personal data should remain restricted.
Verification is not accreditation
A valid Enrolius result means the credential record is attributed to the named provider in Enrolius. It does not prove that the provider is accredited, that a regulator accepts the credential, or that the holder is licensed to practise. Those claims require separate evidence and wording.
Provider responsibilities
Before publishing verification, define correction, revocation, privacy, retention and support policies. Review the public result after every program or template change. Train staff not to edit a credential merely to satisfy a verifier's request.
Standards context
The W3C Verifiable Credentials Data Model describes an issuer–holder–verifier ecosystem and methods for securing claims against tampering. 1EdTech Open Badges 3.0 applies related concepts to achievement credentials. Enrolius's current product promise is provider-attributed public verification; do not imply standards certification unless explicitly documented.
Frequently asked questions
Can anyone open a verification link?
The link is public to a person who has it. Its opaque token helps prevent guessing, but the holder should still share it thoughtfully.
Does verification expose evidence?
It should not expose private evidence by default. The public result should contain only the information needed to understand the credential.
Test the public view
Start your first certification program free. Create one program and add up to three learners—no credit card and no trial deadline.