Short answer: Yes — as of 6 October 2026, Claude works natively inside Google Docs, Sheets, and Slides via a sidebar. It edits documents, writes formulas and builds pivot tables, generates slides from your deck’s theme, and runs on all paid Claude plans. UK Workspace admins can deploy it domain-wide from the Google Workspace Marketplace. This guide covers what it does in each app, how to install, which mode to use, and the cross-app workflows worth building first.
On 6 October 2026, Anthropic launched Claude for Google Workspace: a native sidebar inside Google Docs, Sheets, and Slides. For UK businesses already using Workspace — which is most SMEs outside the Microsoft-heavy sectors — this is one of the most practically useful shipments Claude has made this year. The sidebar removes the copy-paste tax between Claude.ai and the document you’re actually working on.
This guide walks through exactly what the integration does in each app, how to install it individually or as a Workspace admin, the two modes you can run it in, and the cross-app workflows worth building first.
What's actually new
Before 6 October 2026, using Claude alongside Google Workspace meant switching tabs: write in Claude.ai, copy, paste into a Doc, go back to Claude for the next edit, repeat. For teams running multiple documents a day, that friction added up to real hours per week.
The new integration puts Claude in the sidebar of every Google Doc, Sheet, and Slides file. It reads the file, suggests edits (with your approval), writes formulas, builds pivot tables, generates charts, builds entire slides from your deck’s theme, and runs native actions — not just text responses.
Headline features
- Sidebar in all three apps — install once per Workspace account, lives in every file afterwards
- Two modes — "Ask before edits" (approval required) or "Accept all edits" (autonomous)
- Native actions per app — Claude writes real Sheets formulas, builds real pivot tables, inserts real Slides, applies your real deck theme
- Admin controls for Enterprise — Compliance API and customer-managed encryption keys for regulated sectors
Who gets it
Public beta on all paid Claude plans (Pro, Team, and Enterprise). Free-tier Claude users don’t get this. On the Workspace side, it works with personal Google accounts and all Workspace tiers; admins can deploy it domain-wide from the Google Workspace Marketplace.
How to install Claude for Google Workspace
Individual user (fastest)
- Open any Google Doc, Sheet, or Slides file
- Extensions menu → Add-ons → Get add-ons → search "Claude"
- Install, sign in with your paid Claude account
- Sidebar now available in every Google file: Extensions → Claude → Open
Workspace admin (domain-wide deployment)
- Google Workspace Admin console → Apps → Google Workspace Marketplace apps
- Browse apps → find Claude for Workspace
- Install for all users (or specific OUs)
- Approve permissions on behalf of the organisation — users across the domain get the sidebar immediately
Choosing a mode: Ask before edits vs Accept all edits
This is the one choice worth getting right. You set it per document from the sidebar settings cog.
| Mode | What happens | Best for |
|---|---|---|
| Ask before edits | Claude proposes changes as suggestion cards; you accept, reject, or edit each | Client documents, contracts, regulated content, team-shared files |
| Accept all edits | Claude writes directly to the document | Personal drafting, bulk formatting, data cleaning, speed over caution |
Our recommendation for UK businesses: set "Ask before edits" as the default. Switch to "Accept all" per-document when working alone on something low-stakes. For firms in law, accountancy, financial services, or anywhere compliance matters, keep "Ask before edits" on across the board.
What Claude does in Google Docs
- Edit sentences and paragraphs — "tighten this", "make this more formal", "rewrite in British English"
- Restyle headings — reorganise structure, apply consistent hierarchy, generate a document outline
- Suggestion cards — proposed edits appear as Google Docs native suggestions, exactly like a human reviewer in track-changes mode
- Bulk rewrites — apply the same tone adjustment across every paragraph in a 10-page document in one pass
- Document-aware Q&A — "which clauses reference indemnity?", "summarise the three most important actions from this meeting note"
Highest-leverage workflows
- Client letter drafting from a one-line brief, in your firm’s template and tone
- Meeting-note tidying — raw dictation to structured decisions/actions/follow-ups
- Contract redlining — onerous-clause flagging as suggestion cards
- Report polishing — structure and tone pass after drafting
What Claude does in Google Sheets
- Writes formulas from plain English — "calculate 20% commission on anything in column C over £500" → Claude writes and places the formula
- Builds pivot tables — describe what you want to see, Claude configures it
- Native Sheets charts — "chart this as a line graph with months on the X axis" → chart appears, properly formatted
- Adds new tabs with calculated outputs — dashboards, summaries, filtered views
- Data cleaning in Python — messy data (inconsistent dates, mixed-case names, extra whitespace) cleaned via Claude running Python on your sheet
Highest-leverage workflows
- Weekly pipeline dashboards from CRM exports
- Management accounts formatting — TB export in, pivoted summary + variance analysis out
- Commission or tiered-pricing calculations
- Supplier data cleaning (messy quote data standardised)
What Claude does in Google Slides
- Builds new slides from your deck’s layouts and themes — respects master, uses your fonts and colours
- Content-first drafting — "generate a 6-slide pitch deck for a client in [industry] with [key points]"
- Readability checks — flags overlapping elements, text too small to read at projection size, inconsistent capitalisation
- Theme application — apply your deck’s theme to slides pulled in from other files
Highest-leverage workflows
- Client-pitch deck drafting — one-line brief to themed 6-10 slide deck
- Weekly team update decks
- Training / CPD material built from existing documentation
- Readability clean-up pass before a live client meeting
The three cross-app workflows worth building first
The real power is combining the three. These three examples are where UK businesses typically see the biggest week-one wins:
Workflow A: The weekly pipeline review
- Sheet: export fresh deal data from CRM. Claude builds the pivoted weekly dashboard tab.
- Doc: open your weekly review doc template. Claude reads the dashboard, drafts the narrative commentary.
- Slides: Claude pulls the top numbers + narrative, generates the 4-slide team-meeting update deck.
Previously 60-90 minutes manual. Now ~15 minutes of review and polish.
Workflow B: The client proposal
- Doc: write a one-paragraph brief at the top of the proposal doc. Claude expands it into the full proposal using your template structure and tone.
- Sheet: Claude writes the cost breakdown as a Sheet tab, with configurable assumptions.
- Slides: Claude generates the client-presentation deck from the proposal doc + cost sheet.
Workflow C: The year-end client review
- Sheet: load the year’s billing/activity data. Claude builds the "year in numbers" pivot.
- Doc: paste the client’s correspondence history + Sheet summary. Claude drafts the year-end review letter referencing specific moments.
- Slides: Claude builds the 5-slide "year review" deck for the client meeting.
Admin and governance considerations
If you’re rolling this across a team, three things to decide up front:
- Default mode: set "Ask before edits" as the organisational default. Users switch to "Accept all" per-doc when working alone.
- Data access: Claude only reads documents the user already has access to via Google Workspace permissions. No extra exposure — and uploaded Workspace content on paid Claude plans isn’t used for training.
- Audit trail: suggestion-card mode leaves a track-changes trail. For compliance-sensitive sectors, keep users in that mode and keep Google’s version history active (default on).
For firms in regulated sectors (legal, accountancy, financial services), Enterprise plans add the Compliance API and customer-managed encryption keys — worth considering if your sector requires it.
What this does and doesn’t replace
What it replaces: the copy-paste tax between Claude.ai and Google Workspace. The context-switching mental cost of "where did I ask that again?". The friction that stopped most people from using Claude on routine daily docs.
What it doesn’t replace: Claude.ai itself. For long-form reasoning, multi-document analysis, Projects, voice guides, or anything that doesn’t live in a Google file, you still open Claude.ai directly. The sidebar is additive, not a replacement.
What it changes about Microsoft Copilot: for UK businesses evaluating "AI inside the apps I use", the choice is now cleaner. If you’re on Workspace, Claude in the sidebar competes directly with Copilot’s Microsoft 365 integration — and for professional writing, document reasoning, and voice-controlled output, Claude generally wins on quality. If you’re on Microsoft 365, Copilot is still the native choice.
For a side-by-side on this, see our Claude vs Microsoft Copilot comparison and the broader Claude vs Gemini piece.