What is a Student?
In Nimbu, a student is a user who has been enrolled in a class to complete training. Unlike staff roles, which carry permissions to create content, manage classes, and review assessments - the student role is focused entirely on the learning experience: accessing units, completing assessments and observations, and viewing results.
Understanding the student role helps administrators and trainers manage student records accurately, ensure compliance fields are populated, and troubleshoot access issues when they arise.
What's Covered in This Article
This article introduces the student user role and how students interact with Nimbu.
- The Student Role Explained: What a student can and cannot do within the platform.
- How Students Access Nimbu: How student accounts are created and how students log in.
- Student Account Fields: The profile fields that make up a student record, including compliance-critical information.
- Student vs Other Roles: How the student role differs from Admin, Trainer, and Content Editor roles.
The Student Role Explained
The student role is a read-and-complete role. Students can only interact with content that has been specifically assigned to them through their class enrolment. They cannot create, edit, or manage any platform content, and they have no visibility into other students' work or the administrative areas of the platform.
Students can:
- View their enrolled classes and the units within them.
- Access learning resources (articles, PDFs, videos, podcasts, SCORM packages, quizzes, and Canva content...) assigned to their units.
- Complete and submit assessments and observations.
- Use the Michi AI Tutor Assistant on learning material pages.
- View their assessment results and unit progress.
- Accept final unit results (when required by the RTO).
- Complete Pre-Course Materials (PCM) and the Pre-Training Review (PTR).
- Update their own profile details and password.
Students cannot:
- Access any other student's records or submissions.
- View or edit any class, course, unit, or content configuration.
- Access the Marking Dashboard or any administrative settings.
- Enrol themselves in classes without going through a registration workflow configured by the RTO.
How Students Access Nimbu
Student accounts are created in one of three ways:
- Manually by an administrator or trainer: A staff member creates the student profile directly in the Student Registry or adds the student to a class via Class Management, which creates the profile simultaneously.
- Via bulk import: Administrators upload a CSV or Excel file containing student details to enrol a cohort at once.
- Via self-registration: If the RTO has configured a microsite or online registration portal, students can register themselves. Depending on the RTO's settings, registrations may be approved automatically or require an administrator to approve them manually.
Logging In
Once a student account is created and the student is enrolled in an active class, they receive invitation emails with their login credentials. Students access Nimbu by navigating to their RTO's training portal URL and entering their registered email address and password.
Students who have forgotten their password can use the Forgot Password link on the login page to request a reset email.
Note: A student profile can exist in the system without being enrolled in any class. In this state, the student has an account but nothing to access. Students must be added to an active class before they can begin training.
Student Account Fields
Each student in Nimbu has a profile record that stores their personal and compliance information. Some fields are required for the system to function correctly; others are used for AVETMISS reporting and regulatory compliance.
Required Fields
These fields must be completed for a student record to be valid:
| Field | Description |
|---|---|
| First Name | The student's given name. |
| Last Name | The student's family name. |
| Used as the student's login username. Must be unique, no two students can share the same email address in the system. |
System-Generated Fields
Nimbu also assigns the following identifiers automatically when a student profile is created:
| Field | Description |
|---|---|
| Student UID | A system-generated ID used internally to uniquely identify each student record. |
| Enrolment ID | A system-generated ID assigned to each individual student–class relationship, used to track that student's progress within a specific class. |
Student vs Other Roles
Nimbu uses a role-based permission system. The student role is distinct from all staff roles in both scope and purpose. The table below summarises how the student role compares to the three staff roles.
| Capability | Student | Trainer | Content Editor | Admin |
|---|---|---|---|---|
| Complete assessments and learning activities | ✓ | — | — | — |
| View own results and progress | ✓ | — | — | — |
| Mark student submissions | — | ✓ | — | ✓ |
| Manage classes and student enrolments | — | ✓ | — | ✓ |
| Create and manage learning content | — | — | ✓ | ✓ |
| Create and manage courses and units | — | — | ✓ | ✓ |
| Access RTO Settings and platform configuration | — | — | — | ✓ |
| Manage user accounts and permissions | — | — | — | ✓ |
Related Articles
- Core Concepts
- Adding Students
- Student Guide