“Approval” in Digital Insights is primarily informational and/or requires extra steps elsewhere to enforce. Districts frequently want a default stance of:

• Students: block anything not explicitly approved (or newly discovered / unreviewed)

• Staff: allow by default (teachers/admin need tools quickly)

Without a differentiated model, customers either:

• over-block (hurting staff productivity), or

• under-block (increasing student risk/exposure), or

• spend ongoing time maintaining parallel allow/block lists.

In Digital Insights app detail + list view:

• “Approval Status” dropdown: Approved / Unapproved (Students blocked) / Unapproved (All blocked)

• Show effective access:

• Students: Blocked ✅/❌

• Staff: Allowed ✅/❌

• Filters:

• “Unapproved (Students blocked)”

• “Unapproved (All blocked)”

• “Pending Review”

Example Use Cases

• A newly discovered AI tool is unreviewed:

• Block for Students immediately, still allow Staff for instruction planning.

• A known risky app:

• Unapproved (Block All).

• A curriculum tool approved for classroom use:

• Approved.

Value / Impact

• Reduces workload by eliminating duplicated allow/block maintenance.

• Improves student safety posture without disrupting staff operations.

• Supports “default deny for students” policies districts increasingly want.