Skip to main content
AI NewsAI NewsAuto PublishingSEOGrok Google WorkspaceGrok SheetsGrok SlidesGrok DocsGoogle Workspace权限Grok

Grok Enters Google Workspace with a Sidebar for Sheets, Slides, and Docs

The July 24 add-on works inside active files, making Marketplace permissions and reversible testing central to adoption.

ENHE AI5 min4 views
Grok Enters Google Workspace with a Sidebar for Sheets, Slides, and Docs

Key takeaways

SpaceXAI introduced Grok for Google Workspace on July 24, 2026 as one add-on for side-panel work in Sheets, Slides, and Docs. The vendor says it can answer from selected spreadsheet ranges with cell citations, write formulas and charts, extend presentations in an existing theme, and turn rough notes into structured documents. Google Workspace Marketplace lists the add-on as free and discloses permissions to view, edit, create, or delete documents, manage installed spreadsheets, access selected Drive files, display third-party content, connect to an external service, and read account information. Users should review every permission, begin with copies and non-sensitive data, verify citations and edits, test sharing, history, undo, and uninstall behavior, then decide whether administrator deployment is justified.

One add-on covers Sheets, Slides, and Docs.
It supports citations, formulas, charts, and editing.
Marketplace discloses broad file and external permissions.
Start with copies and non-sensitive data.

# Grok Enters Google Workspace with a Sidebar for Sheets, Slides, and Docs

August 16, 2026

Direct answer

Grok's Workspace add-on reduces copying between chat and files, but it requests meaningful file and external-service permissions. Review them and test with non-sensitive copies first.

Fact sources

SpaceXAI announced one Grok add-on for Sheets, Slides, and Docs on July 24, 2026.

The vendor describes cell citations, formulas, charts, slide generation, and structured document editing.

The Google Marketplace listing discloses document, spreadsheet, selected Drive, external service, and account permissions.

Six steps before installing an office AI add-on

  1. Review developer, update date, supported apps, and every Marketplace permission.
  2. Install in a personal test space or approved sandbox, not domain-wide.
  3. Copy a sample file with no customer, contract, credential, or financial data.
  4. Test reading scope, citations, formulas, charts, slides, and document edits.
  5. Check sharing, version history, undo, external connections, account switching, and uninstall.
  6. Write approved tasks, prohibited data, reviewer, and administrator rules.

Why it matters

An office add-on has strong task value because it can edit real files. The same proximity expands accidental changes and data exposure. Free price does not remove governance cost.

Impact for ordinary AI users

Individuals can reduce copy and paste, while teams can accelerate spreadsheet, presentation, and document drafts. Value depends on verifiable citations, reversible edits, and clear data boundaries.

Related tools and tutorials

Start with one reversible task, verify version, permissions, cost, logs, and accepted output, then record the result in a team checklist.

AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news

FAQ

Is the add-on free?

The Marketplace currently labels it free, while account or feature conditions should still be checked at use time.

Can it read my entire Drive?

Review each listed permission and test actual scope with controlled files rather than assuming.

Can an administrator deploy it domain-wide?

The listing supports administrator deployment, but organizations should complete permission and withdrawal testing first.

Source links

  • SpaceXAI: Grok in Google Workspace (2026-07-24)
  • SpaceXAI: Grok for Google Workspace
  • Google Workspace Marketplace: Grok

What this means for everyday users

Record developer, update, account, domain, apps, permissions, file copy, data class, citations, edits, history, sharing, external services, uninstall, administrator, and reviewer.

Related reading

GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts

GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.

Bayer Shares Production Lessons From 22 Specialist Agents: HTTP Success Is Not Task Success

AWS published Bayer Crop Science’s Agentic Decision Engine case study on October 23, 2026. The production system runs 22 specialist agents over governed analytics workflows, models, logs, and visualization tools. This article turns the architecture into five reusable acceptance checks for enterprise agent teams: persist the state needed to resume work, define identity and authorization at every boundary, scope each agent’s tool catalog, distinguish transport success from task success, and release to a gated group before broader access. It also explains why Bayer’s adoption and resolution figures are evidence about one implementation, not promises for another organization. The focus is operational proof, least privilege, rollback, and observable outcomes rather than prompt polish.

GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review

GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.

IskayPet Connects SharePoint to a Managed Knowledge Base: Validate Permissions Before Answers

AWS published IskayPet’s corporate knowledge assistant case study on October 22, 2026. The system connects Amazon Bedrock Managed Knowledge Bases to existing SharePoint repositories and answers cited questions across retail operations, veterinary care, onboarding, and procurement in four languages and three countries. This article turns the case into a practical acceptance plan for knowledge owners. It checks source scope, inherited permissions, hybrid retrieval, duplicate and fragment removal, citation quality, feedback, and token cost before expansion. It also separates the customer’s reported production results from what another organization should expect. A managed retrieval stack reduces infrastructure work, but it does not remove content ownership, access reviews, evaluation datasets, or human verification of important answers.

Copilot in Visual Studio Adds PR Exploration, a BYOM Migration, and NuGet Fixes

GitHub summarized three September updates for Copilot in Visual Studio 2026 on October 22, 2026. The Git agent can explore an attached pull request and link back to comments and files. Bring Your Own Model remains in preview but now requires the new Agent experience, and previously configured Ollama models must be added again. NuGet Audit warnings can open Copilot Chat with the NuGet MCP server to propose dependency fixes. This article gives .NET developers a cautious upgrade checklist: preserve current settings, validate each feature independently, review package and lock-file changes, run targeted tests and vulnerability scans, and keep a rollback path. Summaries and suggested fixes remain review inputs, not verified outcomes.

Amazon Polly Upgrades Generative Speech: Validate 14 New Voices Without Breaking Existing Apps

Amazon Polly upgraded its Generative engine on October 22, 2026, adding 14 voices across nine locales and making generative Hindi and Finnish generally available. Existing voice names and API calls remain unchanged, so applications do not need a code migration, but generated audio can still change. This article gives creators, course teams, contact-center operators, and accessibility teams a reversible acceptance test. It uses one multilingual script to compare pronunciation, pauses, latency, loudness, and fallback behavior before increasing traffic. It also separates the larger voice catalog from a key limitation: generative voices still do not provide speech marks, so workflows that synchronize captions, highlighting, or animation must keep a compatible engine or another timing source.

Summary

Grok in Workspace changes AI from a separate chat into a file-side editor. Permission review, sample copies, task acceptance, and withdrawal testing should precede deployment.

Sources

Table of contents

Latest Insights