{"resourceId":"wsn-nyu-contract-faculty-resolution-disable-gemini-docs-integration-20261028","versions":[{"version":"external-ec59d49726ba1ed639b6ee01033933e8f34be4b2d77549b010495e21279f0ee2","resource":{"id":"wsn-nyu-contract-faculty-resolution-disable-gemini-docs-integration-20261028","title":"NYU contract faculty council asks administrators to disable Gemini’s ability to create and edit Google Docs on student accounts, citing revision-history opacity and course AI policies","organization":"New York University (Full-Time Continuing Contract Faculty Senators Council; AI Leadership Council)","sector":"Higher education teaching, academic integrity and campus AI platform governance","geography":"New York, New York, United States","publishedAt":"Washington Square News, 28 October 2026","publicationDate":"2026-10-28","eventDate":null,"sourceName":"Washington Square News","sourceLabel":"Student newspaper reporting","sourceUrl":"https://nyunews.com/news/2026/10/28/faculty-council-resolution-gemini-integration/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","data-security","operating-model"],"finding":"NYU's Full-Time Continuing Contract Faculty Senators Council passed a resolution earlier in October asking administrators to remove Gemini integrations from Google Docs, Drive and Chrome on NYU accounts. The concern is that students can prompt Gemini outside Docs to create and edit a Google Doc, and if Workspace permissions are enabled the changes appear in revision history as the student's own, undermining a check some professors rely on. The subcommittee chair said the aim is deliberate rather than ambient AI use, not a ban. The council asked for a response on implementation by 1 December. An NYU spokesperson said the AI Leadership Council will review the resolution. NYU has partnered with Gemini since February 2025.","sledRelevance":"Shows faculty governance asking for configuration controls on embedded AI in campus productivity suites, a direct constraint on enterprise AI rollouts aimed at students.","evidence":"Reported resolution text summary, faculty and student interviews and a university spokesperson statement; no usage data.","architectureImplications":"Embedded AI with delegated Workspace permissions can write into documents under the student identity; revision history does not distinguish agent edits.","governanceImplications":"Senate councils can only recommend; the AI Leadership Council review and a 1 December response request set the next checkpoint.","securityPrivacyImplications":"Interpretation: agent actions attributed to a user identity complicate audit trails used in integrity cases.","caveats":"Resolution is non-binding; technical feasibility of disabling the feature is unresolved; perspectives are from a few faculty and students.","streamIds":["student-success"],"roles":{"sales":"Sales framing: NYU's contract faculty want granular control over embedded AI in the campus Google suite, not a ban. That is a common tension where institutions have signed enterprise AI agreements. A bounded engagement could map which embedded AI features are on by default, what admin controls exist, and how faculty course policies can be honoured. Do not claim the resolution shows harm to learning; it reports concerns and a request, and NYU has not decided anything yet.","engineering":"Engineering framing: the technical issue is delegated permissions, where an assistant edits documents and revision history attributes the change to the student. Check what admin console controls exist per service and per organisational unit, whether agent edits can be logged or labelled, and whether course-level scoping is possible. Proof of value should demonstrate a configuration that disables or labels assistant edits for selected groups without breaking other Workspace functions students rely on.","delivery":"Delivery framing: delivery should route this through the AI governance body with IT and faculty senate representation. Work includes an inventory of embedded AI features, a decision record on defaults, communication to students about what is enabled, and guidance for faculty on what revision history can and cannot show. Meet the council's requested 1 December response date with a documented position, even if technical changes take longer."},"roleDetails":{"sales":{"customerProblem":"Institutions with enterprise AI suites lack faculty-acceptable control over embedded AI features that act inside student documents.","stakeholders":["Faculty senate councils","Chief information officer","AI governance council","Academic integrity office","Student government"],"discoveryQuestions":["Which embedded AI features are enabled by default for students?","Can faculty course AI policies be reflected in platform settings?","How are AI-made edits distinguished in audit trails today?"],"valueHypothesis":"Interpretation: a clear configuration and disclosure baseline could reduce faculty-IT conflict over embedded AI without withdrawing access.","potentialEngagement":"Embedded-AI configuration review and governance decision record for a campus productivity suite.","unsupportedClaims":["That embedded Gemini harms learning at NYU","That the feature can be disabled without side effects","That revision history is a reliable AI detector"]},"engineering":{"fit":"Institutions running Google Workspace or similar suites with embedded generative AI for students.","architectureIntegration":"Admin console settings per service and organisational unit; assistant permissions to Docs, Drive and Chrome; audit logging.","prerequisites":["Inventory of enabled AI features","Admin access to service-level controls","Agreed governance owner"],"constraints":["Vendor controls may not be granular to course level","Students can use AI tools outside the managed suite","Resolution is advisory only"],"security":"Agent edits recorded under the student identity weaken audit trails; logging of assistant actions should be confirmed.","proofOfValue":["Test disabling assistant document edits for a pilot group","Verify whether assistant actions appear in audit logs","Confirm other Workspace functions are unaffected"]},"delivery":{"work":"Inventory embedded AI features, take a governance decision on defaults, communicate settings to students and faculty, and publish guidance on audit evidence.","dependencies":["IT admin capacity","AI Leadership Council review","Vendor control availability"],"ownership":"University AI governance council with central IT.","skillsAdoption":"Faculty guidance on what revision history shows; student communication on enabled features and course policies.","governanceCheckpoints":["Council review of the resolution","Documented response by 1 December","Review after any configuration change"],"acceptanceCriteria":["Proposed: written decision on each embedded AI feature default","Proposed: student-facing notice of enabled features","Proposed: tested configuration for opt-out groups"],"risks":["Faculty-IT conflict","Feature cannot be scoped","Students shift to unmanaged tools"]}},"retrievedAt":"2026-10-30T03:21:38Z","enrichedAt":"2026-10-30T03:25:23Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"A council member noted benefits for students who speak English as a second language, alongside cognitive-offloading concerns.","procurementImplications":"Interpretation: enterprise AI agreements should specify admin controls over embedded features and agent-action logging.","operatingModelImplications":"Faculty rely on IT staff to find a way to disable the feature; integrity processes depend on audit data that embedded AI can blur.","sourceVerification":{"openedUrl":"https://nyunews.com/news/2026/10/28/faculty-council-resolution-gemini-integration/","referenceExcerpt":"Contract faculty are urging administrators to disable Google Gemini’s ability to create and edit Google Docs on NYU accounts","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}