Issue

WCPSS supports Lightspeed's planned Access Scan capability that will allow users to submit content to the Lightspeed Content team for review.

Access Scan can already be used contextually from the browser, including while a teacher is viewing YouTube. The primary usability concern is the requirement to manually enter a student email address as part of the Access Scan workflow.

For a teacher who simply wants to determine whether instructional content is accessible to students or submit that content for review, requiring a specific student email creates unnecessary friction.

Operational Impact

The student-email requirement creates several problems:

teachers must know or locate a valid student account;

the workflow becomes dependent on a specific student identity even when the teacher is evaluating content for an entire class;

users may repeatedly enter the same or arbitrary student account simply to perform testing;

the additional step discourages use of an otherwise convenient review tool;

it complicates what should be a quick instructional-content validation workflow.

The request is not to remove identity-aware testing where it is necessary.

The goal is to avoid requiring manual student identity entry when the district's managed environment can provide sufficient context automatically.

Requested Enhancement

Allow Access Scan to determine the appropriate student filtering context without requiring the user to manually enter a student email for every scan or review request.

Potential approaches could include:

Managed Default Test Profile

Allow district administrators to configure a default student test context for Access Scan.

For example:

Default Access Scan Context:

District Student Baseline Policy

Teachers could scan content against that configured context without selecting an individual student.

Organizational Unit or Policy Selection

Allow users to select an approved student scope such as:

Elementary Students

Middle School Students

High School Students

specific school or Organizational Unit

designated Filter policy

This would often be more meaningful than selecting an individual student account.

Automatically Assigned Context

If Access Scan is deployed through a managed Chrome extension, district configuration could provide the appropriate test policy or student context automatically.

The user would simply select:

Scan with Access Scan

and the extension would evaluate the content using the district-defined student context.

Remember Previous Selection

If a specific student or policy must still be selected, Access Scan should at minimum remember the user's previously selected context so it does not need to be entered repeatedly.

Preferred Workflow

The desired experience is:

Teacher encounters instructional content.

Teacher opens Access Scan.

The district-defined student context is already selected.

Access Scan evaluates the URL.

If necessary, the teacher submits the content for Lightspeed review.

No manual student email lookup or entry should be required during the normal workflow.

Identity-Aware Testing

There will still be situations where testing a specific student account is valuable.

Access Scan should retain an optional capability such as:

Test as specific student

for troubleshooting individual policy or assignment issues.

However, this should be an optional advanced workflow rather than a mandatory step for every content scan.

Google Admin / Managed Extension Integration

Because Access Scan can be deployed as a managed browser capability, Lightspeed should consider supporting administrator-configured defaults through managed extension settings.

District administrators could define:

default student policy;

default Organizational Unit or group;

permitted testing contexts;

whether users may select individual students;

whether review submissions are enabled.

This would allow the extension to inherit appropriate district configuration automatically.

Least Privilege Access

Teachers using Access Scan should not require Lightspeed administrative-console permissions.

The extension should provide only the functionality necessary to:

evaluate content against an approved student context;

optionally select another authorized context;

submit content for review.

Administrative policy management should remain separate.

Requested Outcome

Streamline Access Scan so routine instructional-content testing and review submission does not require manually entering a student email address.

The preferred model is:

Open Access Scan → district student context is already known → scan or submit

rather than:

Open Access Scan → locate and enter a student email → scan → repeat for the next request

Acceptance Criteria

This request would be considered addressed when:

Access Scan can operate without requiring manual student email entry for routine scans.

Administrators can define a default student testing context.

The default context can represent a policy, group, OU, or equivalent student scope.

Users can optionally test a specific student when individual troubleshooting is required.

Managed extension settings can supply the appropriate district context where technically possible.

The selected/default context persists between scans where appropriate.

Review submissions can use the same resolved student context without requiring the teacher to re-enter identity information.

Business Value

This enhancement would:

reduce friction for teachers;

increase adoption of Access Scan;

reduce reliance on arbitrary student accounts for testing;

speed instructional-content review;

reduce Help Desk involvement;

make the upcoming SmartPlay review workflow significantly more seamless.

The key improvement is straightforward:

Access Scan should know the student context without requiring the teacher to supply a student email every time.