OpenAI started rolling out a genuinely useful feature this week: ChatGPT Plus, Pro, Business, Enterprise, Edu and Healthcare subscribers can now open a Google Doc, Sheet or Slide from Drive and edit it in place, inside the chat window, without creating a separate copy. Tap Add from Library or mention the file, and ChatGPT edits the actual document stored in Drive. It is convenient, and for a solo user or small team, that convenience is real.
It is also a useful case study in the difference between a feature and a governed system, and it is worth Australian businesses thinking it through before they roll it out past a single power user.
What the coverage flags, and what it doesn't
Secondary reporting on the rollout (OpenAI does not make its announcements easy to scrape directly) flags two limitations worth taking seriously: the integration is not recommended for documents where a collaborator or compliance reviewer needs a visible edit trail, and users running two Google accounts have to switch Drive connections manually.
Read that first limitation again. A tool that edits a live business document in place, with no visible edit trail for a reviewer, is exactly the kind of ungoverned automation that gives compliance teams grey hair. It is fine for a personal Drive. It is a real question for a shared drive with client files, contracts, or anything an auditor might ask about later.
The Claude comparison that actually matters
Claude's approach differs in two ways that matter more than which vendor's assistant is faster to set up. First, Claude's connector model, through MCP, is not locked to one provider's file storage. It is built to plug into whatever system of record a business already runs, Google Drive included, but not exclusively. Second, the patterns Claude Enterprise and Managed Agents ship with default toward approval gates and audit logs on write actions, not silent in-place edits. That is the same governance pattern behind ABC Legal's 50-agent rollout: every action traceable to an owner, every change reviewable.
For an Australian business under the Privacy Act or APRA CPS 230 obligations, can an auditor see who changed this file and when is not a nice-to-have. Before you hand an in-place editing tool to a team, it is worth checking a short list:
Is there a visible record of what the AI changed, and who approved it, that a non-engineer can read?
Can a reviewer see a document's state before and after an AI edit, or only the final version?
Does a write action to a shared file pass through any approval gate, or does it just happen?
If an edit is wrong, can you roll it back and show the trail, or is the original already overwritten?
What is actually at stake
This is not an argument that ChatGPT's feature is bad; it is a reminder that convenience and governance are different purchases. A single silent edit to the wrong shared contract can cost far more to untangle than the feature ever saves. Scoping a properly governed document-AI rollout for a mid-size team, with approval gates and an audit trail your compliance people can actually read, is typically a $6,000 to $12,000 piece of work, and it is a lot cheaper than explaining to a regulator why nobody can say who changed a client file. If you are weighing which AI assistant to standardise on for document-heavy workflows, the right question is not which one edits Google Docs fastest. It is which one you can hand to fifty people without losing the ability to answer for what changed.
How to pilot it safely
None of this means banning the feature. It means piloting it like an adult. Let one or two people use in-place editing on personal or low-stakes drives, keep it away from shared folders holding client files or contracts until you have an edit trail you trust, and write down which document types are in scope and which are not. That gives your team the convenience where it is harmless and keeps it out of the places where a silent change is a problem.
The mistake is the all-or-nothing reflex: either forbidding a useful tool outright, or switching it on across every shared drive because one person liked it. Neither is governance. A short scope, a named owner, and a review of where write actions land is what turns a handy feature into something you can actually stand behind when someone asks what changed.
If you want to scope that properly before rolling an editing tool across your team, book a session and we will map the governance you actually need.
