Hello Reader,

Last week you should have received an email from Google with the subject line "Important updates to your Google Workspace Terms of Service regarding Agentic AI."

If reading through multi-page legal addendums and enterprise cloud clauses left your eyes crossed, you aren't alone. 😵‍💫

Here’s the "non-lawyer" version of the policy change: “If one of your users creates an AI agent that break something or does bad stuff, it’s not our fault.”

This policy change isn’t something you need to panic over, but you do need to pay attention to agents inside of your Workspace environment.

Sponsor

Automate School Chromebook Management with VIZOR

Managing a fleet of Chromebooks shouldn't be a 😱 nightmare. VIZOR is the BEST tool to AUTOMATE common tasks and implement SYSTEMS to make sure things run smoothly:

• ⚡ Automatically assign Chromebooks with a barcode scanner
• 🔂 Identify Chromebooks that students have swapped
• ⬆️ Track devices updates to ensure compliance with state testing requirements
• ❌ Automatically disable lost, stolen, or overdue Chromebooks
• 💦 Trigger a powerwash after an event, such as after a repair

If you are sick of managing Chromebooks through out-of-date spreadsheets and disconnected systems, you need VIZOR! Get in touch for a free demo and pricing!

TOS updates: in plain English

Google updated its education terms of service and introduced new Agentic AI Responsible Use Guidelines. Here is a high-level summary:

1. You own the liability for what your agents do: Google explicitly states that the customer (your school district) is solely responsible for any actions taken by an AI agent operating in your domain. If an agent deletes a folder, shares a confidential student document externally, or misrepresents staff, Google’s position is clear: That’s on you, not the model.
2. "Bypassing Confirmation" is your responsibility: Many agentic tools include built-in safety prompts (e.g., "Are you sure you want to email these 50 parents?"). The new terms warn that if an administrator or user disables these confirmation steps to put tasks on "full auto-pilot," the district assumes all liability for the fallout.
3. Strict bans on surveillance, profiling, and circumvention: The guidelines strictly prohibit deploying agents to bypass file permissions, compile personal profiling data without consent, conducting mass automated monitoring, or hindering emergency services. Nothing too controversial here...I'm sure you don't want your users doing any of these things with their school account!

What Does This Mean for K-12 Education?

Because AI agents operate 24/7, never get tired, and don’t go on vacation, they can be very helpful, or potentially disruptive. The risk is that well-meaning staff (or curious students) will create automated workflows that violate district policy and Google’s TOS.

For example:

• 📨 A building secretary sets up a third-party agent that connects to Gmail and automatically forwards emails containing student registration forms to a personal Gmail account.
• 👩‍💻 A high school computer science student connects a GitHub bot via OAuth that floods Google Drive with thousands of automated API requests.
• 📊 A department head connects an AI tool to evaluate spreadsheets and disables the "confirm before sending" toggle, resulting in mass erroneous emails sent to parents.

👉 Google's updated terms make it clear: Google provides the tools, but you are the pilot.

Upcoming Events for Google Admins

Want to host a Google Admin workshop in your area? Get in touch!

• ​Chromebook Academy (Online) - Nov. 5 - 19, 2026
• ​HECC Conference (Indianapolis, IN) - Nov. 11-13, 2026
• ​Brainstorm Poconos (Pocono Manor, PA) - Nov. 15-17, 2026
• ​Google Admin Bootcamp (Online) - Jan. 7 - 21, 2027)