Notion is coming straight for Google Docs...

Notion has launched “Suggest edits,” a collaboration feature that lets users propose changes directly on a page—creating and deleting blocks—while displaying those proposals as comment-like items that can be approved or rejected. The practical impact is straightforward: teams moving from Google Docs get a familiar workflow for review, where someone with only comment access can still mark up what should change, and someone with edit permission can accept the changes to update the document.

In Suggest edits mode, proposals appear on the page’s right side and can be approved or rejected. Approval requires can edit permission (or can edit on the page), which the workflow demonstrates using a guest account with can comment access versus an admin account with can edit. When suggesting, users can add suggestions for basic content blocks—text, headings, bullet lists, numbered lists, and to-do lists—using a plus button to choose which block types to propose. The feature behaves like Google Docs’ commenting-and-approval model, but with page-level structure: suggestions are tied to specific blocks rather than just inline notes.

There are notable limitations at launch. First, Suggest edits can’t create “child block arrays” from scratch. If a block already has no existing children, a user can’t propose adding indented or nested items under it. For example, an indented bullet list item can only be suggested if that indented structure already exists; otherwise, the nested array must be created by someone with edit access first. The same constraint shows up with callout blocks: if the callout has no child blocks, a guest can’t suggest new blocks inside it.

Second, the interface has some rough edges. The creator notes a janky interaction where users can’t simply “enter down” from a block to start a suggested nested structure; they must insert a blank block via the plus button before selecting the desired block type.

Third, suggested edits can’t be hidden. If someone has edit access, the only way to clear the clutter is to approve or reject suggestions one by one, since there’s no option to temporarily hide proposals and view the clean draft.

Beyond text, Suggest edits also supports deletion. Users can propose removing not just sentences, but entire blocks—including subpages (child pages) treated as blocks within a parent page. The UI label for this is currently ambiguous (“delete block”), and the creator argues it should be clearer (“delete this page”) to avoid accidental removal of whole pages.

Databases are more restricted. While users can suggest edits to text inside table cells, they can’t suggest database property additions/deletions or property value changes, such as changing a tag from “film” to “animation.” Also, Suggest edits can’t propose changes to a page title or create new top-level blocks on a blank page unless an initial child-block array already exists.

Overall, Suggest edits is positioned as a major step for collaborative teams that rely on review cycles, especially those accustomed to Google Docs. The biggest near-term wish list: a way to temporarily hide suggestions, broader block coverage (including richer media like images), and the ability to suggest database property changes—so review workflows can extend beyond basic text into the structured data teams actually manage.