Feature Request: Grade-Based Policy Selection in Access Scan
under review
T
Timothy Cogar
Issue
Access Scan currently requires a teacher to manually enter a student email address to test how a website or resource will behave for students.
While student-specific testing is useful for troubleshooting individual issues, it is unnecessarily tedious for routine instructional use.
Most teachers are not trying to determine whether a resource works for one specific student. They are trying to answer a much simpler question:
Will this resource work for students in this grade?
Requiring an individual student email adds unnecessary steps to what should be a fast validation workflow.
Requested Enhancement
Add a simple grade-level dropdown to Access Scan.
For example:
Test Access For:
Kindergarten
Grade 1
Grade 2
Grade 3
Grade 4
Grade 5
Grade 6
Grade 7
Grade 8
Grade 9
Grade 10
Grade 11
Grade 12
The teacher selects the grade they want to test, and Access Scan evaluates the requested URL against the Lightspeed policy associated with that grade.
There is no need for Lightspeed to determine which grades the authenticated teacher personally teaches.
Providing all configured grade levels keeps the solution simple, predictable, and broadly useful.
Policy Resolution
Lightspeed already receives organizational and policy data through Data Sync.
District administrators should be able to associate each available grade selection with the appropriate student filtering policy.
A simple model could be:
Grade Selection
→ Mapped Student Policy
→ Access Scan Result
For example:
Grade 6
→ Middle School Student Policy
→ Allowed / Blocked Result
This avoids requiring a real student identity when the objective is simply to test policy behavior.
Preferred Workflow
The desired workflow is:
Teacher opens Access Scan.
Teacher enters or scans the instructional URL.
Teacher selects a grade.
Access Scan evaluates the URL against the policy mapped to that grade.
The result is returned immediately.
No student lookup is required.
No student email needs to be copied or entered.
No administrative console access is required.
Specific-Student Testing Should Remain Available
The existing student-email option should remain for cases where an administrator or teacher needs to test the experience of a particular student.
Access Scan could therefore provide:
Test Against:
Grade
Specific Student
The grade option supports routine instructional validation.
The specific-student option supports individual troubleshooting.
Administrative Configuration
District administrators should be able to configure:
which grade levels appear in the dropdown;
which filtering policy is associated with each grade;
whether grade-based testing is enabled;
whether specific-student testing remains available;
which users may use Access Scan.
This keeps policy mapping under district control while keeping the teacher experience simple.
Least Privilege Access
Grade selection should remain a read-only testing capability.
Teachers should not receive:
policy editing rights;
Filter administrative access;
access to policy configuration;
additional administrative privileges.
They simply select an approved grade context and receive the resulting access determination.
Requested Outcome
Allow teachers to test a website against a grade-level student policy without first locating and entering a student email address.
The preferred model is:
Open Access Scan → Select Grade → Scan → Result
rather than:
Open Access Scan → Find a Student → Copy Email → Enter Email → Scan
This would make instructional resource validation dramatically faster and more practical for classroom use, providing teachers with useful answers at — dare we say — Lightspeed.
Acceptance Criteria
This request would be considered addressed when:
Access Scan provides a grade-level dropdown.
All district-configured grade levels can be presented without requiring Lightspeed to determine the teacher's individual teaching assignment.
Each grade can be mapped to an appropriate Lightspeed filtering policy.
Teachers can test resources without entering a student email.
Specific-student testing remains available for individual troubleshooting.
Grade-based testing does not grant policy-management or administrative access.
District administrators control the available grades and policy mappings.
Business Value
This enhancement would:
significantly reduce teacher effort;
make Access Scan practical for routine classroom preparation;
eliminate unnecessary student-email lookup;
encourage proactive testing of instructional resources;
reduce avoidable Help Desk requests;
preserve student-specific testing where needed;
leverage policy information Lightspeed already maintains;
provide faster, more actionable information to instructional users.
The principle is simple:
If the goal is to test a grade-level policy, require a grade — not a student.
Matthew Burg
updated the status to
under review
Autopilot
Merged in a post:
rade-Based Policy Selection in Access Scan
T
Timothy Cogar
Issue
Access Scan currently requires a teacher to manually enter a student email address to test how a website or resource will behave for students.
Student-specific testing is valuable when troubleshooting an individual student, but it adds unnecessary friction to routine instructional use. Most teachers are not asking whether a resource works for one particular student. They are trying to answer a much simpler question:
Will this resource work for students in this grade?
Requiring teachers to locate, remember, or copy a student email makes what should be a very fast validation process unnecessarily tedious.
Requested Enhancement
Add a simple grade-level selector to Access Scan.
For example:
Test Access For:
Kindergarten
Grade 1
Grade 2
Grade 3
Grade 4
Grade 5
Grade 6
Grade 7
Grade 8
Grade 9
Grade 10
Grade 11
Grade 12
The teacher selects the grade they want to test, and Access Scan evaluates the requested URL against the Lightspeed policy associated with that grade.
There is no need for Lightspeed to determine which grades a particular teacher personally teaches. Providing all district-configured grade levels keeps the design simple and predictable.
Policy Mapping
District administrators should be able to associate each available grade with the appropriate filtering policy.
Example:
Grade 6
→ Middle School Student Policy
→ Access Scan Result
A district may use the same policy for multiple grades, which should be supported without requiring duplicate policy configuration.
Preferred Workflow
Teacher opens Access Scan.
Teacher enters or scans the instructional URL.
Teacher selects a grade.
Access Scan evaluates the URL against the mapped student policy.
The result is returned immediately.
No student lookup is required.
No student email needs to be copied or entered.
No administrative console access is required.
Retain Specific-Student Testing
The existing student-email workflow should remain available for cases where an administrator or teacher needs to troubleshoot the experience of a specific student.
Access Scan could therefore provide:
Test Against:
Grade
Specific Student
Grade testing supports routine instructional preparation.
Specific-student testing supports individual troubleshooting.
Administrative Controls
District administrators should be able to configure:
which grade levels appear;
which filtering policy is associated with each grade;
whether grade-based testing is enabled;
whether specific-student testing remains available;
which users are allowed to use Access Scan.
Least Privilege Access
Grade-based testing should remain read-only.
Teachers should not receive:
policy editing rights;
Filter administrative permissions;
access to policy configuration;
additional administrative privileges.
They simply select an approved testing context and receive an access result.
Requested Outcome
Allow teachers to test websites against grade-level student policies without needing to identify an individual student first.
The preferred workflow is:
Open Access Scan → Select Grade → Scan → Result
rather than:
Open Access Scan → Find Student → Copy Email → Enter Email → Scan
This would provide teachers with fast, useful, potentially transformative instructional information at — dare we say — Lightspeed.
Acceptance Criteria
Access Scan provides a grade-level selector.
All district-configured grade levels can be presented.
Each grade can be mapped to an appropriate filtering policy.
Routine testing does not require a student email.
Specific-student testing remains available.
Grade testing does not provide policy-management permissions.
District administrators control grade-to-policy mappings.
Business Value
This would:
reduce teacher effort;
make Access Scan practical for classroom preparation;
encourage proactive testing;
reduce unnecessary Help Desk requests;
preserve precise student-specific troubleshooting;
make better use of policy information Lightspeed already maintains.
Core principle: If the goal is to test a grade-level policy, require a grade — not a student.