OpenAI has expanded ChatGPT's Google Drive integration so eligible paid users can open and edit native Google Docs, Sheets and Slides without leaving ChatGPT, with changes written back to the underlying Drive file. Availability depends on the plan, surface, file type and workspace configuration, and administrators may need to approve the Google OAuth scopes required for write actions.
OpenAI has expanded ChatGPT's Google Drive integration so eligible paid users can open and edit native Google Docs, Sheets and Slides without leaving ChatGPT. Reporting from 9to5Mac says users can add Drive files to ChatGPT Library, ask questions about them and update the underlying file rather than working from a detached copy.
OpenAI's current help documentation confirms that ChatGPT Work can create or edit native Google Docs, Sheets and Slides when the relevant Google Workspace app is enabled and connected. The exact experience varies by plan, file type, workspace settings and product surface, so the rollout should not be interpreted as universal access in every ChatGPT account.
From file retrieval to write actions
Earlier Google Drive connections centered on searching, syncing and using Drive content as context. The new workflow adds an action layer: a user can select a file, request a change and then review the updated file in Google Workspace. OpenAI's instructions explicitly tell users to choose the account or file, approve the action and review the result before relying on it.
That distinction matters. Reading a document helps ChatGPT answer questions; editing the live file changes shared work that colleagues and downstream processes may use. Teams should treat the feature as an operational write path, not just another retrieval connector.
Administrators control the boundary
OpenAI's Google app data-controls documentation says workspace administrators can enable or disable specific app actions. Google Workspace administrators may also need to trust the ChatGPT/OpenAI OAuth app or approve the scopes required by the enabled actions. The documented Google Drive scope set includes capabilities for creating, updating, sharing, moving, up, copying and deleting Drive-family files, though the actions available to an individual user still depend on configuration and permissions.
For enterprise teams, the practical work is governance: enable only needed actions, confirm Google permissions, and make review expectations explicit for shared documents and spreadsheets. The convenience gain is real, but so is the need to distinguish a draft suggestion from a committed change to a live file.
Key Points #
- 1Eligible paid ChatGPT users can open and edit native Google Drive files without leaving ChatGPT, according to OpenAI documentation and independent reporting.
- 2The feature updates the underlying Drive file rather than producing only a detached static copy.
- 3Availability and write authority depend on plan, product surface, file type, workspace settings and approved Google OAuth scopes.
Scoring Rationale #
Direct editing turns a common enterprise content connector into a write-capable workflow with meaningful productivity and governance implications. The impact is broad but configuration-dependent rather than a universal product change.
Sources #
Primary source and supporting public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.