A school I work with recently adopted a policy requiring teachers to minimize student information stored on outside platforms. Even a student’s full name was considered more information than an instructional application needed. A permitted first name was acceptable, but the surname had to be replaced by an alias.
This struck me as a reasonable programming challenge. Could Innovation Assessments provide teachers with the student identities they need to manage a class without requiring personally identifying information the school does not want stored?
The answer turned out to be yes.
What Is Alias-Only Student Identity?
Teachers may now designate an Innovation Assessments course as Alias-Only. Students registered for such a course have an account containing:
- Their permitted real first name
- An unrelated, system-generated alias in place of their surname
- A randomly generated privacy identifier
- A private internal login value rather than a real email address
- Their customary classroom PIN
A student named John, for example, might appear in the course as John Iris with the privacy identifier IA-EF25EA. The word “Iris” has no relationship to the student’s real surname. It is selected from a neutral list by the system.
The student can sign in using the teacher’s Class Number and a four-digit PIN. No student email address is required.
Privacy Without Making the Classroom Unmanageable
There is a practical problem with aliases: teachers still have to know who their students are!
The system therefore retains the student’s permitted first name and pairs it with a memorable word. This is considerably easier for a teacher to manage than a roster of random numbers. The additional privacy identifier gives the teacher a stable reference when two students have the same first name or when records must be distinguished more carefully.
Aliases are generated automatically. Teachers do not have to invent them, and students are not asked to choose amusing screen names that may prove distracting or inappropriate. The purpose is not to disguise the classroom from the teacher. It is to minimize the personal information stored in the application.
Keeping Standard and Alias Accounts Separate
One complication became apparent as I planned this feature. A single student account cannot safely contain a real surname for one course and simultaneously be treated as anonymous in another. The information still exists in the shared account.
Innovation Assessments therefore keeps the two account types separate.
A standard student account may participate in standard courses. A privacy-alias account may participate in Alias-Only courses. If the same student needs access to both kinds of courses, the teacher creates two separate accounts.
The application enforces this distinction. Teachers cannot accidentally assign one account to a mixture of standard and Alias-Only courses.
Converting an Existing Course
A teacher must empty a course’s active roster before changing it to Alias-Only identity.
This sounds more dramatic than it is. Removing a student’s course access does not erase completed submissions or scores. It simply ends that account’s ability to enter the course. Once the active roster is empty, the teacher can enable Alias-Only identity and create new privacy-alias accounts for the students.
This approach avoids trying to rewrite student identities across numerous kinds of assignments, recordings, scorecards, proctoring records, and gradebook entries. As an old programmer, I have learned to respect the opportunities for mischief that come with an unnecessarily clever database operation! A clean boundary is safer and easier for teachers to understand.
The course page explains the procedure and prevents Alias-Only mode from being enabled while ordinary student enrollments remain active.
Privacy Rules That Follow the Course
The setting applies to the whole course rather than to individual assignments. Once Alias-Only identity is enabled:
- Self-registration requests only the permitted first name.
- Google profile autofill is not offered.
- The system supplies the alias and private internal login.
- Teacher-created and batch-created accounts follow the same rules.
- Enrollment controls prevent standard accounts from entering the course.
- Older and direct-access routes cannot bypass the restriction.
Copying a module from the course does not copy its identity policy. The destination course retains its own privacy setting. This is important because instructional content may be reused in schools operating under different guidelines.
Collect Only What Is Needed
Schools differ considerably in their policies governing educational technology. Some permit ordinary student names and school email addresses in approved instructional systems. Others require far greater data minimization.
Innovation Assessments can now accommodate both approaches.
My aim was not to make every classroom anonymous by default. Most teachers do not need that. Instead, the platform now gives an institution the ability to say, “This is all the student information we permit this course to store,” and have the software enforce that decision consistently.
That is much better than placing the entire burden on the teacher to remember which fields to leave blank, which names to alter, and which accounts may be assigned to which courses. Good privacy practices are more dependable when they are built into the workflow.
This feature arose from a subscriber’s real classroom need. That is how many of the best additions to Innovation Assessments begin: a teacher encounters a practical problem, we think through what would make the work easier and safer, and then the platform becomes a little better for everyone.
Transparency note: This article was generated with AI assistance based on the implemented Innovation Assessments feature and writing samples supplied by David Jones. It is published under a separate author identity to distinguish AI-assisted posts from articles written personally by David.
