> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/national-learner-registry-and-digital-credentials.md).

# National Learner Registry & Digital Credentials

A reproducible DIY toolkit for a national learner registry and digital credentials — built on DPI building blocks, proven in a live ITU Sandbox.

This Knowledge Product shows how to build a national learner registry and a digital-credential issuance system — diplomas, certificates — on top of Digital Public Infrastructure building blocks: digital identity, information mediation, Verifiable Credentials, and digital wallets. It follows one continuous journey: **learner registration** → an **authoritative learner registry** record → **certificate or diploma issuance** → a **digitally signed Verifiable Credential** → the learner's **digital wallet** → **third-party verification**.

{% embed url="<https://www.youtube.com/watch?index=1&list=PLOj17GZ2k4ew&v=_BQCrnOl5tY>" %}

{% hint style="info" %}
This Knowledge Product is grounded in a working **Proof of Concept**, built on Digital Public Infrastructure principles and deployed in the **ITU Sandbox** environment. The PoC demonstrates technical feasibility, interoperability, and the core end-to-end flows — it is not production-ready and is not intended for national-scale deployment. Its purpose is to prove the approach and serve as the concrete reference behind this material.
{% endhint %}

## Build It Yourself

The core idea is **DIY**: a team in another country can replicate this PoC on its own, without custom development from scratch. Three connected parts make that possible — the written Knowledge Product, a step-by-step video series, and a live sandbox users can try directly.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-book-open" style="color:$primary;">:book-open:</i></h4></td><td><p><strong>Read the Knowledge Product</strong></p><p>The full written material — architecture, data model, roles, signing and credential issuance — in both business language and configuration detail.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/why-this-matters.md">Why This Matters</a></td></tr><tr><td><h4><i class="fa-clapperboard" style="color:$primary;">:clapperboard:</i></h4></td><td><p><strong>Follow the DIY Videos</strong></p><p>A 16-video series — roughly 4–5 hours in total, most episodes capped at 20 minutes — that walks through configuring each low-code component of the PoC step by step, with no coding required.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/video-learning-path.md">Video Learning Path</a></td></tr><tr><td><h4><i class="fa-flask" style="color:$primary;">:flask:</i></h4></td><td><p><strong>Explore the Sandbox</strong></p><p>A live ITU Sandbox deployment demonstrates the same workflows shown in the material: a public Education Portal for registration, enrolment and credential issuance, and a private Registry Environment holding the underlying registries, connected through X-Road. <a href="https://cabinet.liquio.assembly.govstack.global"><strong>Open the Education Portal</strong></a> to try it yourself.</p></td><td><a href="https://cabinet.liquio.assembly.govstack.global">https://cabinet.liquio.assembly.govstack.global</a></td></tr></tbody></table>

{% hint style="info" %}
The sandbox is split across two environments connected through **X-Road**, the secure data-exchange layer. The public **Education Portal** runs registration, enrolment and credential issuance; a separate, private **Registry Environment** holds the National Learner Registry and National Certificate Registry, which contain personal learner data and are kept isolated from the public side — the two environments never communicate directly.

The public Education Portal can also be accessed via **eSignet**, using your own official identification credentials rather than a shared login. See [eSignet authentication](https://docs.esignet.io/esignet-authentication) for details.
{% endhint %}

## Why It Matters

Learner records and credentials are often fragmented across institutions — held on paper or in disconnected databases that don't talk to one another. Verifying a certificate typically means contacting the issuing institution directly, achievements are recorded inconsistently across institutions, and a learner's history doesn't travel cleanly with them when they move between schools, regions, or countries.

A registry-backed, standards-based credential model closes each of these gaps: credentials are issued as verifiable digital objects a verifier can check cryptographically without contacting the issuer, a common data model keeps achievements consistent across institutions, and because the learner holds their own credential, their record travels with them.

See [Why This Matters](/experience-digital-transformation/national-learner-registry/why-this-matters.md) for the full case, including the Giga/DPI context and this Knowledge Product's objectives.

## What You'll Learn and Build

The material follows a learner through the full registry-to-credential journey: how a learner profile is created and validated in the **National Learner Registry**; how a certificate or diploma becomes a signed **Verifiable Credential**; how that credential is issued, digitally signed, and delivered to a **digital wallet**; and how a third party verifies it without contacting the issuer. Along the way it covers the identity, information-mediation, and e-signature building blocks the ecosystem depends on, and how the pieces interoperate under open standards rather than a single vendor's conventions.

## Who This Is For

|                                                                        |                                                                                                                                                                                                                                |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p><strong>Implementers</strong><br>Architects & engineers</p>         | How to configure the registry, credential, signing and wallet workflows, and how the architecture, data model and integration points fit together.                                                                             |
| <p><strong>Government</strong><br>Ministry of Education teams</p>      | What a national learner registry and digital-credential ecosystem involves end to end, how it aligns with Digital Public Infrastructure principles, and what would need to change to move from a PoC to a national deployment. |
| <p><strong>Ecosystem partners</strong><br>Wallets, relying parties</p> | How credentials are issued, signed, stored and presented; what a wallet or relying party needs to support to interoperate with the registry; and how a presented credential is verified.                                       |

## Explore the Knowledge Product

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-lightbulb" style="color:$primary;">:lightbulb:</i></h4></td><td><p><strong>Why This Matters</strong></p><p>The credential recognition problem, and how a registry-backed, standards-based model solves it.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/why-this-matters.md">Why This Matters</a></td></tr><tr><td><h4><i class="fa-layer-group" style="color:$primary;">:layer-group:</i></h4></td><td><p><strong>Architecture and Standards</strong></p><p>The platform's functional systems, and how they fit together — by capability, not by product name.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/architecture-and-standards.md">Architecture and Standards</a></td></tr><tr><td><h4><i class="fa-bullseye" style="color:$primary;">:bullseye:</i></h4></td><td><p><strong>Use Case Scope</strong></p><p>The two business processes, the key actors, and what this Proof of Concept does not attempt to solve.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/use-case-scope.md">Use Case Scope</a></td></tr><tr><td><h4><i class="fa-database" style="color:$primary;">:database:</i></h4></td><td><p><strong>Learner Registry</strong></p><p>Registration and enrolment, the data schema, roles and permissions, and verification.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/learner-registry.md">Learner Registry</a></td></tr><tr><td><h4><i class="fa-certificate" style="color:$primary;">:certificate:</i></h4></td><td><p><strong>Digital Credentials</strong></p><p>From certificate data to signed, wallet-held, verifiable proof.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/digital-credentials.md">Digital Credentials</a></td></tr><tr><td><h4><i class="fa-server" style="color:$primary;">:server:</i></h4></td><td><p><strong>Deployment and System Integration</strong></p><p>Environments, cloud deployment, access, and integration with external systems.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/deployment-and-system-integration.md">Deployment and System Integration</a></td></tr><tr><td><h4><i class="fa-plug" style="color:$primary;">:plug:</i></h4></td><td><p><strong>DPI Integrations</strong></p><p>X-Road for information mediation, eSignet for digital identity, and the iGrant Wallet.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/dpi-integrations.md">DPI Integrations</a></td></tr><tr><td><h4><i class="fa-circle-play" style="color:$primary;">:circle-play:</i></h4></td><td><p><strong>Video Learning Path</strong></p><p>The video modules that accompany the written material.</p></td><td><a href="/experience-digital-transformation/national-learner-registry/video-learning-path.md">Video Learning Path</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/national-learner-registry-and-digital-credentials.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.