> 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/learner-registry.md). # Learner Registry Registration and enrolment, the data schema, roles and permissions, and verification — how a learner becomes a trusted record in the National Learner Registry. A learner enters the ecosystem through **Student Registration & Enrolment**, and the outcome of that process is an authoritative record in the **National Learner Registry**: a single, trusted representation of the learner that certification, credential issuance, and verification all build on afterward. The GovStack Digital Registries specification defines a registry as an authoritative collection of records representing entities within a specific domain. In this use case, the learner profile represents the learner as an entity within the education ecosystem — created once, through a governed process, and reused everywhere the learner's identity needs to be trusted. {% embed url="" %}


	Registration and Enrolment How a learner profile is created, and how registration differs from enrolment.
	Data Schema and Registry Structure What a schema is, required fields, data consistency, and schema versioning.
	Roles, Permissions and Institutional Access Key roles, role-based access control, and how institutions interact with learner records.
	Verification, Status and Audit Trail How learner data is checked, who can verify it, and how every change stays traceable.

*** {% columns %} {% column %} **Previous**\ [Use Case Scope](/experience-digital-transformation/national-learner-registry/use-case-scope.md) {% endcolumn %} {% column %} **Next**\ [Digital Credentials](/experience-digital-transformation/national-learner-registry/digital-credentials.md) {% endcolumn %} {% endcolumns %} --- # 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/learner-registry.md?ask=&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.

:user-plus:

:table-cells:

:users-gear:

:clipboard-check: