Dark mode
Block-based editing

Block-based editing

Every document in Docs is made of blocks — a paragraph, a heading, a list, a callout, a table, an image, an embed. Each block keeps its own identity as the document changes, which is what lets you comment on, link to, and review a single block instead of the whole page.

Why blocks matter

  • Comments and links stay put — a block stays the same block while you edit around it or move it, so comments, links, and proposals stay attached to the right content.

  • Precise review — a suggested change can target one block, so reviewers see exactly what would change.

  • Clear history — version history and per-block last-edited-by info answer "who changed this, and when?"

Adding and moving blocks

  • Add a block — type / to open the slash menu and pick a block (see Slash commands & block types), or use markdown shortcuts as you type: # for a heading, - for a bullet, 1. for a numbered list, > for a quote.

  • Move a block — grab the ⠿ handle to the left of any block and drag it; a drop indicator shows where it will land.

  • Block actions — the same handle opens actions for that block: duplicate, delete, comment, and copy link.

What you can do with blocks

  • Comment on any block (see Inline comments & proposals / review).

  • Link a block to a task, epic, deal, conversation, or any other workspace object (see Link to CRM / PM / support objects, block-level links).

  • Share a link to a block — use Copy link from the block's handle.

  • Embed entities and saved views (see Mentions & entity mentions and Saved view embeds).

  • Ask AI to regenerate an AI-generated section — the new version is reviewed before it replaces anything.

Blocks and AI agents

Agents work with the same blocks you do. When an agent suggests an edit, it arrives as a change proposal for either the whole document or a single block, and nothing changes until someone with edit permission applies it (see Inline comments & proposals / review).

You rarely need to think about blocks when writing — but they're the reason Docs features stay precise instead of string-matching on text.

Was this article helpful?