FOR SCHOOL IT
A managed installation.
A clear support path.
One extension, configured for your school. No AI runtime or extension data server.
Managed package status: preparation
This is the deployment route, not a ready-to-install package. Signing, the matching Google OAuth client and school pilot checks must pass before a package/update URL is published here.
Choose supported browser management
Use your established Chrome Enterprise/Education policies on supported managed browsers or devices. Ordinary Windows/Mac users cannot install a self-hosted package simply by clicking a download.
Review the release package
Check the extension ID, version, package checksum, permissions, privacy notice and update source. A self-hosted signing identity must match its OAuth configuration; do not assume it matches a Store build.
Configure access by tool
Allow the Google services your school approves. Classroom uses current teacher membership. Forms requests access on import. Email sending is optional. Genesis Calendar needs a supported site adapter and independently approved teacher/year/term configuration.
Pilot before wider deployment
Verify a designated account, source accuracy, simultaneous tools, cancellation, duplicates and account switching. Use synthetic student records for demonstrations. Preserve Google sharing settings.
Install and maintain
Use the verified signed package and HTTPS update manifest with school policy. Stage updates, retain the previous release and test rollback. Keep signing credentials private.
What remains with the school
Google consent does not override school restrictions. Role selections do not authorize records. Scheduled school jobs remain in their existing systems; Chrome must be running for interactive extension work.
Your school does not need access to the private development repository to install. Installed extension code is still inspectable; packaging does not make browser code secret.