Claude Can Now Edit Your Google Docs Directly

Anthropic announced Claude for Google Workspace on October 6, in public beta on all paid Claude plans. It adds a sidebar beside an open Doc, Sheet or Slides file, reads the file, sees what you have selected, and makes changes in place. A separate set of Docs, Sheets and Slides connectors, also in beta, lets Claude create and edit Google files from a chat conversation instead.

What it does in each app

The Sheets description is the most substantial of the three, because pulling a range into Python for a join and writing the result back covers the work most people do badly with nested formulas. The Slides self-check is the most unusual, since a tool reviewing its own output for overlapping elements and unreadable text is doing a job that normally falls to whoever opens the deck five minutes before a meeting.

Two modes, one decision

Anthropic describes a default mode that asks before edits, where each change appears as an approval card with a summary and Claude waits. The alternative accepts all edits and works through the task without stopping.

Credit where it is due: shipping with approval as the default is the right call, and plenty of products have shipped the other way round. The risk now sits with how long that default survives contact with a deadline, because the second mode is genuinely faster and the person choosing it is the person in a hurry.

Treat the mode as policy rather than preference, and tie it to the document rather than to the user. Approval required on anything a customer receives, anything contractual, pricing, procedures and any figure that reaches a financial statement. Automatic is fine on drafts and internal analysis. The sorting exercise takes an afternoon and is set out in document control when AI can edit the file.

Approval cards are not free review

An approval card asks you to read a change and decide. Click it forty times in a morning and you are confirming rather than reviewing, which is the fatigue problem that shows up wherever volume meets a per-item gate.

The defence is deciding in advance what you check on a given document, which on most of them is the numbers, the names, the dates and anything stated as a commitment. Reading a proposed change for general plausibility produces a judgment about tone, which is rarely the thing most likely to be wrong, as covered in quality assurance when AI writes the first draft.

Someone has to switch it on

The add-on installs from the Google Workspace Marketplace and opens under Extensions. The connectors that let Claude edit Google files from a chat are separate, and on Team and Enterprise plans an owner or primary owner has to enable them before anyone can use them.

That is one decision with a workspace-wide effect, which makes it worth recording: who enabled it, when, and which parts. Integrations that gain write access to a system of record are the ones businesses most often cannot account for later.

Version history will not answer the question

Google's version history records what changed and which account changed it. An edit applied by an assistant on your behalf and an edit you typed both appear as you editing the document.

For internal reports that is fine. For a priced quotation or a procedure, the question an auditor or an insurer asks is who approved this, and an entry showing that an account saved it does not answer that. Where it matters, record the approval somewhere outside the tool that made the change.

Where this sits competitively

Gemini has been available natively in Workspace for some time, so the practical change is choice of assistant inside Google's own apps rather than a new category of capability. Microsoft has offered the equivalent inside Office, and the comparison for Excel specifically is in how to use Copilot in Excel.

For a business already standardised on Claude, the value is removing the shuttling of text between a chat window and a file. For anyone evaluating assistants, the model comparison is in ChatGPT versus Claude versus Gemini, and the lighter-weight route into Sheets is connecting Google Sheets to ChatGPT.

A sensible first week

Install it for two or three people rather than the whole company. Leave approval mode on. Point it at working files and internal analysis, not at anything a customer will see, since this is a public beta and betas have rough edges. Ask the group to note what it got wrong, because that list is what tells you where to trust it.

Before widening access, sort your documents into controlled and working, decide who may enable connectors, and decide where approvals get recorded. Those three answers cost less to produce now than to reconstruct from version history later.

Frequently Asked Questions