The Reusable Blocks sidebar contains organization-wide content that can be
shared across documents: legal clauses, product descriptions, standard terms,
disclaimers, and other repeated sections.
Create and edit a block
- Open Reusable Blocks in the editor sidebar.
- Click the add button.
- Enter a name, optional description, category, and tags.
- Write the content in Rich text or Markdown mode.
- Optionally add a short changelog note and save the block.
Blocks are stored as Extended Markdown and versioned when their content is
updated. Metadata-only edits such as changing a category do not create an
unnecessary version. Categories and tags make larger libraries searchable.
You can also right-click a supported block in the visual editor and choose
Save as reusable block. Autype opens the same create flow with that
document section as the initial content.
Insert into a document
Place the editor cursor where the block should appear, then choose:
Referenced blocks display their name and resolved content in the rich text
editor. Edit the source block from the sidebar instead of modifying the linked
content directly.
You can also drag a block from the sidebar to the current editor position.
Drag-and-drop always creates a Reference, never a copied snapshot.
History, restore, and detach
Open Library → Reusable blocks for a searchable table of all blocks. Choose
History on a row to review every published version, its changelog note,
timestamp, rendered preview, and source Markdown.
Choose Restore this version to return to earlier content. Restore never
deletes or overwrites history: it copies the selected content into a new current
version and records which version it came from. This keeps existing pinned
references deterministic and makes every rollback auditable.
A reference can follow the block’s latest version or stay pinned to one
specific version. When a newer version exists, update the pinned reference from
its context toolbar. To customize linked content only for the current document,
choose Detach; the resolved block becomes ordinary editable document
content and no longer receives library updates.
The document stores fallback content with a reference so conversions and
previews remain deterministic even if the library item is temporarily
unavailable. Organization permissions still control access to the source block.
Use references for centrally maintained content. Use copies when the inserted
text must be customized for one document.
