D
Connector · Google Docs
Approvals, coming to Google Docs
A native Google Docs approval workflow: request, review and sign off from a side panel next to the document, with status visible in-document the whole time. Same Workspace SSO, same workflow engine, same audit trail as Word and Confluence. We’ll start once those two are live.
Join as a design partner
See how OneApproval works →
Planned after launch
The research
Google Docs is the second most-requested platform in our approval research.
We surveyed more than 450 people about how document approval actually happens today. Microsoft 365 came out on top. Google Workspace came second, both for current usage and for where people most want something better.
450+
people surveyed on how document approval actually happens
#2
most-wanted platform to improve, right after Microsoft 365
61%
work with documents that need approval on more than one platform
What we’re planning
Same platform. Native to Google Docs.
The Google Docs connector will handle the approval process end to end: request, review and sign-off, without leaving the document. The heavy lifting stays in the OneApproval platform — Docs just surfaces what matters, where you are.
01
Status in the margin.
A glanceable status badge next to your Google Doc, the same idea as the indicator already live in Word and Confluence.
02
One workflow engine.
Same workflows, same approvers, same audit trail you already use in OneApproval. It just runs inside Docs too.
03
Workspace SSO.
Sign in with your existing Google Workspace identity. No second account, no separate password.
04
External approvers welcome.
Send a sign-off link to reviewers outside your Workspace, the same way Word and Confluence approvals already work.
05
Request from the doc.
Start a Google Docs approval request from the side panel: pick a workflow, add approvers, send. No switching tabs, no copying links.
06
One process, every platform.
The same approval process whether the document started in Google Docs, Word or Confluence. One audit trail, no matter where it was written.
Built for real documents
The documents Google Docs teams tell us matter most.
Our research into how approval work actually happens keeps surfacing the same handful of document types. The Google Docs approval workflow is being designed around those, not a generic comment thread.
Project & reporting docs
Status updates, project plans and reports that need a manager’s sign-off before they go out. The approval request stays tracked next to the doc, not buried in a comment thread.
Technical documentation
Specs, runbooks and technical docs that need review from more than one stakeholder before they ship, with a clear record of who signed off on which version.
Policies & SOPs
Policy and procedure documents where process owners need a clean, exportable audit trail. It’s the same standard OneApproval already holds Word and Confluence documents to.
The bigger picture
Google’s built-in approvals are fine, for Google.
Google Workspace can route a comment or an assignment inside Docs. It can’t approve a Word document, a Confluence page or a Miro board with the same audit trail. In our survey, 61% of people said they work with documents that need approval on more than one platform. OneApproval covers that gap with one flow and one audit trail, no matter where the document lives.
See the full platform story →
Help us plan what comes after Word and Confluence.
Design partners get early access when it ships, founding-partner terms, and a say in what we build first. We haven’t started development yet. Your input can still shape the plan.
Join as a design partner
