> 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/registration-and-enrolment.md). # Registration and Enrolment How a learner profile is created, and how registration differs from enrolment. ## What Learner Registration Means Learner registration is the process through which a learner profile is created in the National Learner Registry. Its purpose is to establish a uniquely identifiable learner record that can be reused across education services and administrative processes. 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. Once created, the profile can support subsequent processes such as certification, credential issuance, and credential verification. The registration process becomes available after the applicant has authenticated through the ID Building Block — in this implementation, via eSignet. Before the registration form is displayed, the system checks the National Learner Registry using the applicant's National ID number. If a matching learner record already exists, the registration process cannot proceed. This prevents duplicate learner profiles and supports the integrity of the registry. ## What Enrolment Means — and How It Differs From Registration {% hint style="info" %} Enrolment is the process through which a learner's relationship with an educational institution is established. While **registration** creates the learner profile, **enrolment** records information about the learner's intended participation in the education system. {% endhint %} Within Student Registration & Enrolment, registration and enrolment are completed through a single application journey. However, the information collected serves different purposes: registration focuses on learner identity and profile creation, while enrolment captures institution-specific information such as the selected educational institution, residential address, support requirements, and, where applicable, prior education history. This distinction reflects a common GovStack registry design principle in which core entity information is maintained separately from information describing relationships, affiliations, or service participation. A learner's identity remains stable, while enrolment information may change over time. ## Actors in the Registration and Enrolment Process The GovStack Workflow Building Block defines workflows as sequences of tasks, decisions, and transitions assigned to specific actors. Each actor performs a defined role that contributes to the creation of a trusted learner record. The process begins when the learner authenticates via eSignet. The applicant then completes the registration and enrolment application, uploads supporting documents, reviews the generated application document, and confirms submission. The **School Registration Officer** performs the first review of the application, validating the submitted information and supporting documents and deciding whether the application should proceed or be rejected. The **MoE Registrar** performs the final approval — reviewing the application, recording a decision, and signing the generated decision document using the confirmed server-side digital signature mechanism, a custom in-house solution. ## What Data Is Collected During Registration The GovStack Digital Registries specification recommends maintaining structured records based on defined schemas. Information collected during registration therefore follows a predictable structure that supports validation, storage, retrieval, and reuse. **Personal information** includes the learner's first name, last name, National ID number, phone number, email address, and date of birth. Several of these attributes are pre-filled using identity data received from the identity provider. **Enrolment information** includes the selected educational institution, residential address, special support requirements, and optional prior education history — applicants may provide information about up to five previous educational institutions and upload supporting evidence where applicable. The process also requires **supporting documents**: proof of identity, a passport-sized photograph, proof of address, and optional prior education documents. Before submission, the system generates an *Application for Student Registration & Enrolment* document that consolidates all submitted information into a single PDF for applicant review and confirmation. ## Validation and Approval Steps Validation and approval are workflow activities performed before a learner profile can be created in the National Learner Registry. The Student Registration & Enrolment process applies a two-stage review: 1. The **School Registration Officer** examines the submitted information and supporting documents and records one of two decisions: **Validate** or **Reject**. Rejected applications leave the workflow, and the applicant is notified of the outcome. 2. Applications that pass validation proceed to the **MoE Registrar** for final review, who records an **Approve** or **Reject** decision. When an application is approved, the system generates a formal decision document, which is reviewed and signed using the confirmed server-side digital signature mechanism. When an application reaches a validation or approval stage, the system automatically creates a task for the appropriate actor and sends a notification. Each decision determines the subsequent workflow transition, application status, and notifications, ensuring every application is processed by the appropriate role at the appropriate stage. ## What Happens After Registration Is Completed Once the MoE Registrar approves the application and signs the decision document, the approved information is used to create the learner record. The GovStack Digital Registries specification describes registry records as authoritative representations of entities that can be reused across services and business processes. Following approval, the learner profile becomes the authoritative representation of the learner within the National Learner Registry. The system first assigns a **Unique Learner Identifier (ULID)** — a persistent reference usable across education services, certificates, and digital credentials. The system then creates the learner record in the National Learner Registry using the approved application data. {% hint style="success" %} After the learner record has been created, the application status changes to **Awaiting QR Code Generation**, and a new task is assigned to the applicant. Through this task, the applicant generates a learner profile QR code linked to a W3C Verifiable Credential representing the learner profile. The credential can be downloaded or added to a digital wallet and serves as a portable and verifiable representation of the learner's registered status. {% endhint %} These outputs — ULID generation, learner record creation, status updates, notification delivery, and the QR code task — provide the foundation for subsequent processes such as certification, credential issuance, and credential verification. --- # 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/registration-and-enrolment.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.