From the Campus Operations edition of October 29, 2026
NYU faculty senators demand the unpublished Google Workspace and Gemini contract terms, admin settings and data definitions before 12 November
New York University · Higher education IT governance · New York, United States
- Publisher
- NYU Full-Time Continuing Contract Faculty Senators Council
- Original publication
- Resolution approved 6 October 2026; memo dated 7 October 2026
- Source retrieved
- 2026-10-30
- Event date
- 2026-10-06
What happened
NYU's contract faculty senators asked IT to share the unpublished license terms under which Gemini is provided as a core Google Workspace service, including the data processing addendum, the admin settings for enabling or disabling Gemini, and how the agreements define student, aggregated and deidentified data. They note that assurances that Gemini does not train on or log university data are not backed by documents available to faculty. They want written reasons for any withholding, notice of configuration changes, and the materials before their 12 November 2026 meeting.
Why it matters
AI features arriving inside existing productivity suites often bypass new procurement review. Why now: the 12 November deadline is two weeks away, and this week Princeton and Hebrew University announced AI licensing with contract assurances that faculty cannot inspect.
Evidence and measured results
Text of an approved faculty council resolution; NYU's response not yet known.
Limitations and uncertainty
Advocacy document; claims about missing documentation reflect the council's view; dated earlier this month.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- AI features in existing suites lack terms faculty can inspect.
- Stakeholders
- Chief information officer
- General counsel
- Provost
- Faculty senate technology committee
- Discovery questions
- Which AI features are enabled by default?
- Can contract data terms be shared under confidentiality?
- How are configuration changes announced?
- Value hypothesis
- Interpretation: proactive disclosure could reduce governance conflict; no outcome is reported.
- Potential engagement
- A bounded AI terms and configuration disclosure review for one suite.
- Unsupported claims
- That NYU's terms are inadequate
- That Gemini trains on NYU data
- FERPA noncompliance
Pre-sales engineering
Role takeaway
- Fit
- Fits institutions with AI enabled inside Google Workspace or Microsoft 365.
- Architecture and integration
- Admin console settings controlling AI features by organizational unit, with data processing terms.
- Prerequisites
- Admin configuration export
- Data processing addendum
- Data classification map
- Constraints
- Contract confidentiality
- Vendor privacy policy definitions
- Security
- Clarify logging, training and deidentification commitments for AI features.
- Proof of value
- Export current AI settings by user group
- Map each data category to FERPA handling
Delivery
Role takeaway
- Work
- Create a standing disclosure process for AI terms and settings.
- Dependencies
- Legal review
- IT admin access
- Governance committee schedule
- Ownership
- IT governance office with general counsel.
- Skills and adoption
- Plain-language briefings for faculty committees.
- Governance checkpoints
- Terms shared or withholding explained in writing
- Configuration change notices issued
- Periodic governance review
- Acceptance criteria
- Proposed: materials delivered before the governance deadline
- Proposed: every AI configuration change logged and announced
- Risks
- Legal limits on sharing
- Trust erosion if withheld
- Settings drift without notice
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Gemini enabled as a core Workspace service; admin configuration governs who gets AI features.
Governance
Who approves, reviews and stays accountable for outcomes?
Faculty want contract terms and configuration changes disclosed to shared governance.
Security and privacy
What data, permissions and controls need testing?
Undefined deidentified and aggregated data categories raise FERPA questions.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Faculty seek control over AI features in teaching platforms.
Procurement
What should contracts, pricing and exit terms secure?
AI added through an existing suite license rather than a new contract.
Operating model
Which teams own the service once it runs?
IT may need a standing disclosure process for AI terms and settings.
Publication history
- 2026-10-29Campus Operations · Issue 525 resources
Stable resource ID: nyu-cfsc-resolution-google-workspace-gemini-terms-20261006