Google adds staff review options to document automation

Google is giving document automation a way to ask for review before changing the words. In its Google Workspace announcement, the company says developers can now create, read and manage comments through the Google Docs, Sheets and Slides APIs. Google Docs also gains support for suggested text edits, allowing connected tools to propose revisions for a person to review rather than alter the document directly.

According to Google, the capabilities differ across the three products:

• Docs: automated tools can add, review and reply to comments, and submit proposed text changes as suggestions.
• Sheets: tools can add, review and reply to comments on specific cells.
• Slides: tools can add, review and reply to comments linked to individual slides or specific presentation elements.

Google says the gradual rollout began on 30 September 2026, with up to 15 days for feature visibility. Availability covers all Google Workspace customers and people with personal Google accounts. The announcement describes capabilities for developers and connected systems, so treat it as something to discuss with whoever builds or maintains your automation.

Keep the proposed change beside the work

For a business of five to fifty people, the useful possibility is an approval step inside the document your team is reviewing. Google explicitly describes automated tools proposing Google Docs revisions for user review. That gives you a concrete design option: let a system prepare a change, then leave the judgement with a staff member.

Consider a possible workflow for a customer proposal. You could ask your automation provider to have a tool suggest revised wording in Google Docs, with comments explaining what needs attention. Your nominated reviewer would then assess those proposals. This is an example to explore, not a ready-made workflow Google says it has supplied.

For spreadsheets and presentations, plan around comments. A possible reporting workflow could leave a comment on a cell that needs checking, or beside a slide element that needs clarification. Google's announcement supports those comment locations; it only announces suggested text edits for Docs. Keep that distinction clear when discussing what you want built.

The practical question is whether a proposed change reaches someone responsible for reviewing it. Before commissioning anything, decide who owns that review, what they should check and when the work is ready to proceed. Treat those as workflow decisions your business needs to make.

Start with one review step and check access

Choose one recurring document process to assess, such as reviewing a proposal before it goes to a customer. Ask the person responsible for your automation whether these capabilities are available in your setup, and request a small demonstration using a sample document.

• Define the output: specify whether you want comments, suggested Docs text changes, or both.
• Name the reviewer: decide who will examine each proposed change and what approval means for that process.
• Check app access: review which connected apps should have access to your Workspace data.

Google says there is no admin control or end user setting for this feature itself. However, admins can control which apps access Workspace data, and users can manage connections between their Google Account and third-party apps. Google also says comment support through its Model Context Protocol servers remains in developer preview. If a provider proposes that connection method, ask them to explain how its preview status affects the proposed workflow.