Using Text Blocks

Text Blocks are reusable pieces of content that you define once in Settings and then reference in your document templates. They are useful for boilerplate language that should appear consistently across projects, such as company descriptions, standard disclaimers, methodology overviews, or any content that doesn’t change on a per-project basis.

How Text Blocks Work

Each Text Block has two parts:

• Name: A descriptive label (e.g., “Company Overview” or “Standard Disclaimer”). The name must be unique within your account.
• Content: The actual text, which supports Markdown formatting. You can use bold, italic, bulleted lists, numbered lists, and other Markdown syntax. The content is converted to formatted HTML at document generation time.

When you save a Text Block, the platform automatically generates a Merge ID (slug) from the name. This slug is what you use to reference the Text Block in your document templates.

Dynamic Content with Merge Fields

Text Block content supports Handlebars-style merge fields. You can insert project-specific data into your boilerplate by wrapping field names in double curly braces:

{{client_name}} has engaged {{business_unit_name}} to deliver
the services described in this Statement of Work.

At document generation time, these fields are replaced with actual project values, so the same Text Block can produce customized output for each project.

The {{decimal}} and {{currency}} helpers are also available for formatting numeric values:

The total project investment is {{currency total_revenue}}.

Using Text Blocks in Templates

Text Blocks are available as merge data in your document templates. In a V2 Tag Template, reference a Text Block using its slug under the text_blocks namespace. Use the double-tilde (rich text) tag so the Markdown content renders as formatted text:

{~~project.text_blocks.company_overview}

In a V1 Mail Merge template, the slug is available as a top-level merge field:

«company_overview»

The content is rendered as formatted HTML, preserving any Markdown formatting you applied in the Text Block editor. For how that content is styled in your document — controlling list font, and how this differs from V1’s ListNumber/ListBullet styles — see Styling rich text and lists.

Managing Text Blocks

Text Blocks are managed in Settings. The Text Blocks page shows a table with the Name and Merge ID for each block. From here you can:

• Create a new Text Block by clicking the Add button at the bottom of the list.
• Edit an existing Text Block by clicking its row.
• Delete a Text Block using the delete control on its row.

The settings.text_blocks permission controls access to this page. Users need at least View access to see Text Blocks, and Manage access to create, edit, or delete them.

When to Use Text Blocks vs. Other Features