Claude for Google Workspace illustration with hands stacking white blocks on an orange background — Anthropic's official graphic for Claude for Google Workspace. Image: Anthropic.

Our team writes proposals in Google Docs, tracks budgets in Sheets and pitches in Slides. So when Anthropic launched Claude for Google Workspace this week, it got my attention fast. It puts Claude in a sidebar right next to your open file, and it can edit that file for you.

Anthropic shared the news on October 6, 2026, in its post Claude now works with Google Docs, Sheets, and Slides. Investing.com also reported on the new add-on and connectors the same day. I went through both, plus the help guide. Here is what actually changed, and what agency teams in India and the USA should do about it.

What Anthropic Launched on October 6

There are two separate pieces in this release. It helps to keep them apart, because they work in opposite directions.

The Claude for Google Workspace add-on. You install it once from the Google Workspace Marketplace. Claude then appears under the Extensions menu in Docs, Sheets and Slides.
Google Docs, Sheets and Slides connectors. These let you start in the Claude app and have it create or edit Google files from the chat.

Both are in public beta on all paid Claude plans. Anthropic's help guide lists Pro, Max, Team and Enterprise. You also need a Google account that is allowed to install Marketplace apps.

One install covers all three apps. You do not need three separate extensions.

How Claude for Google Workspace Works Inside Your Files

Once installed, you open a file and go to Extensions, then Claude, then Open Claude. A sidebar opens beside your document. Claude can read the file, see what text, cells or slides you have selected and make changes in place.

Google Docs Extensions menu showing the Claude option with Open Claude and Help — Opening Claude from the Extensions menu in Google Docs. Image: Anthropic Help Center.

In Google Docs

Claude can fix a sentence or restyle a heading without breaking the formatting around it. For bigger rewrites, it can show suggestion cards in the sidebar. Each card highlights the passage it wants to change, and you apply or dismiss it.

Anthropic's own example is a good one. You can ask Claude to tighten an executive summary and turn the next steps into a table. It does both inside the doc.

In Google Sheets

This is where I expect most agencies will see value first. Claude can write formulas, build pivot tables and charts, and add new tabs. For joins or data cleaning, it can pull a range into Python and write the results back.

The help guide suggests prompts like "find why the VLOOKUP in the Summary tab returns #N/A for some rows and fix it." Anyone who has debugged a client's budget sheet at 11 pm knows why that matters.

In Google Slides

Claude builds new slides from your deck's existing layouts and themes, so they match the rest of the deck. It can also check its own work. It flags elements that overlap, run off the slide or are hard to read.

You Control How Much It Does Alone

There are two modes at the bottom of the sidebar:

Ask before edits (default). Claude explains each change and waits for you to click Allow.
Accept all edits. Claude makes ordinary content edits without stopping.

Even in the second mode, some actions always need your approval. Claude stops before it inserts an image from a web address, adds a link or removes anyone's access. There is no "always allow" option for those.

Claude also cannot share the file, give anyone access or change who owns it. It refuses those requests even if you ask.

What Claude Can and Cannot See

This is the first question any client will ask. The answer is fairly reassuring, as long as you understand the two pieces.

Inside the add-on, Claude sees only the file you opened it in, plus any connectors you turn on. It asks Google for two core permissions. One lets it show a sidebar. The other lets it view and manage the file it was installed in. Google enforces that limit.

Google permission screen listing the access Claude requests for documents, spreadsheets and presentations — The Google permission screen shown the first time you open Claude in a file. Image: Anthropic Help Center.

The connectors are different. When you edit Google files from the Claude app, Claude can reach any file your Google Drive permissions allow. That is far wider access, so treat it with more care.

On data handling, the help guide makes a few clear points:

Anthropic says it does not use this content to train its models.
Inputs and outputs are deleted from Anthropic's systems within 30 days, with some exceptions listed in its policies.
The extension does not inherit custom data retention settings your organization may have set in Claude.
Chat history is saved locally in your browser, per file, and does not sync across devices.

That third point is easy to miss. If your team has agreed a shorter retention window with a client, check how it applies here before you roll this out.

On Enterprise plans, the Compliance API, customer-managed encryption keys and OpenTelemetry audit export also cover the add-on.

Current Limits of Claude for Google Workspace

It is a beta, and Anthropic is upfront about what it cannot do yet. These are the limits I think agency teams will hit first:

One file at a time. In the add-on, Claude cannot open, create or copy other files in Drive. It also cannot export a PDF.
Keep the sidebar open. Closing it stops the current task.
No Firefox. Use Chrome, Edge or Safari. In Firefox the sidebar loads but actions do not complete.
A six-minute cap. Google stops a single long operation after about six minutes. Break big jobs into stages.
No comment handling in Docs. Claude cannot read, reply to or resolve comments. Its edits land as direct edits, not suggestions.
Static charts in Slides. Charts it creates are images, so they will not update when the numbers change.
No live BigQuery tabs. Connected Sheets tabs cannot be read or edited. Extract the rows to a normal tab first.

You can attach up to 20 reference files per message, with a 30 MB limit per document and 10 MB per image. That is plenty for a brief, a CSV export and a brand guide.

How Agencies in India and the USA Should Use It

Most of our projects have a team in India and a client in the USA. Both sides live in shared docs and sheets, so a tool like this touches real client data from day one.

Good First Use Cases

These are the jobs I would hand over first, because a person can check the output in minutes:

Cutting a long project brief down to a one-page summary for a client.
Turning meeting notes into a table of owners, actions and due dates.
Explaining an inherited spreadsheet, such as "how is the total in H42 calculated?"
Normalising messy dates or names in a lead list before import.
Splitting a text-heavy slide into two clean ones that match the deck.

Picture a coordinator preparing a monthly report for a US retail client. The numbers sit in a Sheet and the story goes in a Slides deck. Claude could build the pivot table, flag lines over budget and draft the summary slide. The coordinator then reviews everything before it goes out.

Questions Your Clients Will Ask

US clients often send security questionnaires before they approve a new tool. Expect questions about who processes their data, how long it is kept and whether it trains a model. Anthropic's answers above give you a starting point.

For Indian agencies, the Digital Personal Data Protection Act puts duties on anyone handling personal data. If a sheet holds customer names, phone numbers or emails, decide who may open Claude on it.

The simple rule I follow: if you would not paste it into a chat window, do not open Claude on that file until the client agrees.

Setting Up Claude for Google Workspace Safely

Here is the rollout plan I would use for a small or mid-sized agency:

Start with internal files. Try it on your own templates and reports before any client document.
Control who installs it. Many companies block Marketplace apps by default. Google explains how to manage the Marketplace app allowlist in its Workspace admin help.
Use admin install for groups. Super admins can deploy Claude to selected groups or organizational units, so only your pilot team gets it.
Keep "Ask before edits" on. Let people see every change during the first few weeks.
Hold off on the connectors. They reach any file the user can access in Drive, so enable them later and on purpose.
Use version history. Every Claude edit is saved under the user's name, so you can roll back anything.
Write a one-page policy. Note which client files are off limits and who signs off on AI-assisted work.

Anthropic's Claude Help Center guide covers install steps and limits in more detail. If you are on a startup budget, our post on free Claude Team access and AI credits for startups explains how to get a paid plan at lower cost. For the policy side, see our guide to AI agent governance for agency teams.

Key Takeaways

Claude for Google Workspace puts Claude in a sidebar inside Docs, Sheets and Slides, and it is in beta on all paid plans.
New connectors let Claude create and edit Google files from the chat, with access that matches your Drive permissions.
The add-on only sees the open file and any connectors you enable. Anthropic says it does not train on this content.
Key limits include one file at a time, no Firefox support, a six-minute task cap and static charts in Slides.
Pilot it on internal files with "Ask before edits" on, and control installs through the Google Admin console.

Want help fitting AI tools like this into your delivery process without risking client data? Our team offers software development consulting for agencies and growing businesses.

About the Author

Nitin Kumar is Lead Project Coordinator at Debugged Pro. He manages software and AI delivery for startups and growing businesses in India and the USA, and most of his planning happens in shared Docs and Sheets. He writes about practical, low-risk ways for teams to adopt new tools.