K-12 AI Governance & Tool Intelligence
For Educators Who Read Carefully · languagefirm.org/districtfiling
Tool Spotlight
Gemini is Google's general-purpose generative AI assistant, accessible via gemini.google.com, mobile apps on iOS and Android, and integrated side panels across Google Workspace. This card assesses Gemini as a Core Service in Google Workspace for Education, accessed through a school-provisioned Workspace account. That access path activates enterprise-grade data protections under the Google Workspace for Education Terms of Service and the Cloud Data Processing Addendum: chats are not used to train generative AI models, are not reviewed by human reviewers, and are not shared outside the organization's trust boundary.
The consumer Gemini app (gemini.google.com signed in with a personal Google account) operates under a different privacy notice, trains on user data by default, and allows human review of some chats. That consumer path is categorically out of scope for this card and should not be used for any district-sanctioned deployment. The product surface does not distinguish between the two paths; the distinction is entirely governed by which account is signed in.
Gemini was elevated to a Core Service for all Workspace for Education editions (Fundamentals, Standard, Plus) as of the June 30, 2025 ISTE announcement, and is available at no additional cost to students of all ages when Admin age-based access settings are correctly configured. The paid Google AI Pro for Education add-on (formerly Gemini Education / Gemini Education Premium) extends Gemini into the side panel of Docs, Sheets, Slides, Gmail, and Meet; most premium features remain restricted to users 18 and older even with a paid license assigned.
Best Use Cases10 Things Every Educator Needs to Know
Google Gemini earns Teacher-OK at 17/20. The score is conditional on one requirement that is not optional: school-provisioned Workspace for Education account access. Every protection on this card is activated by that account. Every risk on this card is created by using any other account. That is the whole governance story.
Scope discipline is the whole card. The account used to sign in determines whether every protection below applies or not.
Every protection on this card is activated by school-provisioned Google Workspace for Education account access. The consumer Gemini app, accessed with a personal Google account at gemini.google.com, is categorically out of scope and must not be used for any district-sanctioned deployment. The product surface does not distinguish between the two paths. A teacher or student who opens gemini.google.com with their personal account sees the same interface as one who opens it with their school account. The governance consequences are not subtle: consumer path trains on user data by default, permits human review, and carries no GWFE contractual protections. This distinction must be named explicitly in every staff guidance document the district produces for this tool.
Data training status depends entirely on the access path. The contract is the protection, not the product.
Under a Workspace for Education account, chats are not used to train generative AI models and are not reviewed by humans. This is established contractually under the Google Workspace for Education Terms of Service and the Cloud Data Processing Addendum, not through a product feature or UI setting. The consumer app path trains on user data by default and permits human review of some chats. Districts should treat these as two separate products that share a name, a URL, and an icon. The contractual path is the governed path. The consumer path has no place in district deployment.
Gemini is ON by default as a Core Service. Admin configuration is required before student rollout, not after.
For all Workspace for Education editions (Fundamentals, Standard, Plus), Gemini is enabled by default following the June 30, 2025 Core Service elevation. Admins must proactively configure age-based access and organizational unit controls in the Admin console before student rollout. A district that has not audited these settings since June 2025 should treat Gemini as potentially live for students already. The Admin console paths that matter are: Generative AI settings (age-based access toggle), Apps scope by organizational unit, and audit logging for Gemini activity. None of these configure themselves.
Age handling is bifurcated and admin-driven. The youth experience activates only when the Admin console is correctly configured.
Gemini in Workspace for Education is available to students of all ages, but the youth experience (no image generation, automatic fact-check prompts on factual queries, tighter content filters, AI literacy onboarding) activates only when the Admin console age-based access setting is correctly configured for users under 18. For students under 13, the district must also verify that those students are placed in an organizational unit where Gemini is scoped to the youth experience and that the Admin console age-of-user setting reflects their actual age. The product does not auto-detect user age from account data. The district is responsible for the configuration.
COPPA responsibility sits with the school. Google supports compliance. The school is the operator.
For students under 13, the district must obtain and document parental consent before enabling Gemini, and must verify the Admin console places those students in the youth experience. Google's published guidance confirms COPPA support under the GWFE agreement. However, under COPPA's school-as-operator framework, the school authorizing tool use for educational purposes assumes the obligation to ensure the tool is used only for educational purposes and that data collection is limited accordingly. A generic AUP sign-off does not satisfy this obligation for an AI tool the district specifically enables. Documented, tool-specific consent tied to the student record is the required standard.
The paid add-on does not unlock full features for minors. Assigning a license does not change the age restriction.
Google AI Pro for Education (formerly Gemini Education / Gemini Education Premium) extends Gemini into the side panel of Docs, Sheets, Slides, Gmail, and Meet. Most premium features remain restricted to users 18 and older even with a paid license assigned. A district that purchases the add-on and assigns licenses to students under 18 will not unlock the full premium feature set for those students. This is a deliberate product design decision, not a configuration gap. Districts evaluating the paid add-on for student use should confirm current age-gated feature availability with Google before purchasing.
Retention is admin-configurable, not automatic. Set it against your record retention policy before rollout.
Conversation history in Gemini defaults to 18 months and can be configured to 3, 18, or 36 months, or turned off entirely in the Admin console. Districts should set this against their own record retention policy before rollout, not after staff have built up conversation history. Retention configuration also affects whether Gemini activity is retrievable in response to a FERPA records request. The default of 18 months is not a governance position; it is a product default. The district's record retention schedule is the governance position. Align the two before students and staff begin using the tool.
Gemini is not source-grounded like NotebookLM. Treat output as a draft to verify, not a finished artifact.
Gemini output draws from training data and the open web, not only from user-uploaded documents. Hallucination risk on factual content is meaningfully higher than with NotebookLM, which grounds responses in documents the user provides. For tasks requiring factual accuracy, staff guidance should treat Gemini output as a draft requiring primary-source verification before it is published, assigned to students, or used to inform a governance decision. Staff PD for Gemini should include a module on recognizing confident-sounding but unverified claims, and should name specific task types where NotebookLM or primary-source research is the more appropriate tool.
The Common Sense Privacy Seal is in place. Third-party vetting signals are strong for the Workspace path.
Gemini in Google Workspace for Education earned the Common Sense Privacy Seal in the June 29, 2025 evaluation. Google documents support for COPPA, FERPA, and HIPAA workloads with ISO/IEC 27001, 27017, 27018, 27701, 42001, SOC 1/2/3, and FedRAMP High attestations. These certifications apply to the Workspace for Education contractual path. They do not apply to the consumer Gemini app. For districts that use Common Sense Media ratings or SDPC listings as procurement prerequisites, the Common Sense Privacy Seal satisfies one of those signals for the Workspace path specifically.
17/20 is a strong Teacher-OK. Three documented gaps: Q9, Q15, Q20. None are governance blockers today.
Total: 17/20. Section 6: 5, Section 7: 4, Section 8: 4, Section 9: 4. The three gaps are: no formal retraining guidance published when new Gemini features ship (Q9, Section 7), no public privacy policy version history allowing districts to track changes over time (Q15, Section 8), and no independent K-12 outcome data specific to Gemini's impact on student learning (Q20, Section 9). None of these are governance blockers today. All three are worth tracking in subsequent drift audits. The 17/20 score reflects a product with real governance infrastructure deployed on a contractual path that activates meaningful protections. The Teacher-OK label is earned on the Workspace account path. It does not transfer to the consumer path.
Evidence Links: For Your Internal Verification Routine
Endurance Skills Guide
Gemini's governance story turns on one variable: the account used to sign in. That variable cannot be managed by a policy document alone. It requires a set of durable operational skills that translate across every vendor that uses the same "same product, different account, different governance" model. These six endurance skills are built from Gemini's specific story and generalize directly to the next tool.
01
Access-Path Discipline
Treating the Account as a Governance Artifact, Not a Convenience
Before enabling or recommending any AI tool, identify which account type activates which protections and build that distinction into staff guidance and AUP language. For Gemini, this is the difference between Teacher-OK and categorically out of scope. The skill is naming the account in every policy document, not just the tool. "Gemini is approved for staff use" is insufficient. "Gemini is approved only when accessed through the district-provisioned Google Workspace for Education account" is the governance statement the distinction requires.
02
Admin Console Literacy
Knowing What Your Console Can and Cannot Enforce Before Assuming a Policy Is Live
Walk the Admin console paths for any tool you deploy: Generative AI settings, age-based access, organizational unit structure, retention, audit logging. Document the current state in writing rather than assuming defaults match intent. For Gemini, the relevant paths are the age-based access toggle under Apps, the OU scope for Gemini activity, and the retention setting under Data and Privacy. None of these configure themselves. A district whose governance document says "youth experience is enabled" should be able to produce a screenshot of the Admin console confirming that statement.
03
Age-Based Access Verification
Confirming Youth Experience Configuration Every Year, Not Just Once
Audit the OU structure for students under 13 and under 18 against the age-based access setting before every school year and whenever a vendor changes a default. Treat youth-experience configuration as a standing operational check, not a one-time setup task. For Gemini, the risk is not that the setting will disappear. The risk is that a domain migration, a new OU, or a feature expansion shifts the default without triggering an alert. A scheduled annual audit of the Admin console age-based access configuration is the minimum operational standard for any district deploying AI tools to students.
04
Consent Documentation
Parental Consent Exists Only If It Is Documented and Retrievable
For any tool enabled for students under 13, keep a district-retained record of parental consent tied to the specific tool, the date, and the consenting adult. A generic AUP sign-off does not satisfy COPPA for an AI tool the district specifically enables. For Gemini, this means a tool-specific consent notice that names Gemini, describes what data is collected under the GWFE agreement, and identifies the district as the operator responsible for ensuring educational-purpose use. The record should be retrievable by student in response to a parent request.
05
Source-Groundedness Judgment
Matching the AI Tool's Output Mechanism to the Stakes of the Task
For factual or student-facing content, favor source-grounded tools (NotebookLM) over open-web generative tools (Gemini), or require that staff verify Gemini output against primary sources before publishing or assigning. Build this distinction into staff PD, not just IT policy. The question to ask about any AI tool before assigning it to a content task is: does this tool generate from training data and the open web, or does it ground responses in documents I provide? The answer determines the verification burden. Gemini is the former. Districts should set staff expectations accordingly before the tool is in use, not after a hallucinated fact reaches a student.
06
Drift Monitoring
Every AI Tool's Governance Posture Changes. Assume Yours Does Too.
Subscribe at least one admin to the vendor's updates blog (Google Workspace Updates for Gemini), designate someone responsible for translating substantive changes into staff guidance, and revisit the DPA and policy signals on a scheduled cadence rather than reactively. Gemini's Core Service elevation happened June 30, 2025. The February 3, 2026 feature expansion changed what premium features are available to which users. The April 13, 2026 Classroom language expansion changed the Classroom integration scope. Three substantive changes in under a year is the normal cadence for a major AI platform. Drift monitoring is not a one-time task. It is an operational role.
Gemini presents the sharpest access-path fork in the District Filing series to date. The same product name, the same URL (gemini.google.com), the same app icon, and the same interface behave differently depending on whether the user is signed in with a personal Google account or a school-provisioned Workspace for Education account. The governance consequences are not subtle. Personal account: trains on user data by default, permits human review, 18 and older to register. School account: no model training, no human review, contractually protected under GWFE Terms of Service and Cloud Data Processing Addendum, available to all ages with Admin-configured youth experience. The tool does not warn the user which mode they are in. Nothing about the product surface makes the distinction visible to the user.
Access-Path Discipline is the skill of treating the sign-in account as a governance artifact, not a convenience. It has three operational expressions. First, AUP language that names the account specifically. Instead of "Gemini is approved for staff use," write "Gemini is approved only when accessed through the district-provisioned Google Workspace for Education account. Access through any personal Google account is a policy violation." The specificity is not bureaucratic. It is the only language that survives the moment when a teacher, working from home on a personal device, opens gemini.google.com and signs in with whichever account is cached.
Second, device-level controls where possible. On district-managed Chromebooks, scoping browser sign-in to Workspace accounts removes the ambiguity at the device layer rather than relying on staff memory. This is not a universal solution, it does not cover personal devices, and it does not help when a staff member switches accounts. But it eliminates the most common accidental exposure: the managed device where a personal account happens to be signed in.
Third, a staff PD module that shows both access paths side by side. The difference is invisible at the product surface but total at the governance layer. Staff should see the two paths once, clearly, with the consent and data handling consequences of each named explicitly. They should also know how to check their own sign-in state: the Google account avatar in the upper right corner of gemini.google.com displays the account currently in use. That check takes three seconds and should be part of onboarding for every staff member enabled to use the tool.
Practitioner Exercise
Open gemini.google.com on any device you have access to. Confirm which Google account is currently signed in by checking the avatar in the upper right corner. If it is a personal account, note how long it would take you to detect that if you were a teacher opening the tool for the first time. Then open your district's current AUP or acceptable use guidance for AI tools. Check whether it names "Gemini" or "Google Workspace account" as the approved access path. If it names the tool but not the account, you have identified a policy gap that exists right now. Draft one sentence that closes it and bring it to your tech director or curriculum coordinator at your next check-in. That sentence is the minimum unit of Access-Path Discipline.
Most Recent Policy Update
Core Service: June 30, 2025 · Feature Expansion: February 3, 2026 · Classroom Language Expansion: April 13, 2026
On June 30, 2025, at the ISTE conference, Google announced that the Gemini app became a Core Service in all Google Workspace for Education editions (Fundamentals, Standard, Plus). Core Service status means the product is available at no additional cost, included under the GWFE Terms of Service and CDPA, and enabled by default for all domains. For districts that had not evaluated Gemini before this date, the announcement meant the tool was potentially live for students and staff without any district action. For districts that had evaluated Gemini as a paid add-on, the announcement changed the pricing and access model, not the governance model. The contractual protections that apply to Core Services under GWFE are the same as those that applied to the paid add-on.
On February 3, 2026, Google extended select Gemini in Workspace features (Docs, Slides, Forms, Vids) to Education Plus and Teaching and Learning users 18 and older, on a rapid release and scheduled release rollout window. This expansion did not change the age restriction on premium features, but it did change the product surface for adult users in Workspace for Education. Districts should verify that their current Admin console configuration reflects intended access for this expanded feature set.
On April 13, 2026, Gemini in Google Classroom expanded to all Classroom-supported languages across Education Fundamentals, Standard, and Plus editions. This change affects districts operating in non-English languages and should be noted in any district whose staff or students use Classroom in a language other than English.
Three operational implications for districts. First, Gemini is now on by default for new Workspace for Education domains; inaction is a deployment decision. Second, the age-of-access envelope has widened to all ages for Core Services, which shifts COPPA and youth-experience configuration from an optional consideration to a required pre-deployment step. Third, the Gemini feature surface is expanding on a rolling basis, which means the governance signals documented on this card can drift between issue cycles. Assign an admin to monitor the Google Workspace Updates blog and revisit this card's policy signals at each drift audit cycle.
Archive
Every issue of The District Filing, archived and searchable by topic, tool, and skill focus.
languagefirm.org/districtfilingarchive