# Text

Plain body text. Use it for descriptions, instructions, supporting copy, or anywhere you need a paragraph rather than a heading.

## Available in

* Page modules
* Order Form modules
* Dashboard modules
* Public Page modules

Text isn't available in Catalog, Modal, Reports, or Navigation modules.

## When to use

* Description below a heading.
* Instructions inside a form ("Add items to the order using the catalog or barcode scanner").
* Welcome messages, status notes, or anything that's prose rather than data.
* Footer text or fine-print on a page.

For headings, use **Heading**. For inline buttons that look like text, use **Button** with variant=link.

## Settings

| Setting       | Description                                                |
| ------------- | ---------------------------------------------------------- |
| **Text**      | The text content. Supports multi-line.                     |
| **Size**      | M (default body size, 20px) or S (smaller, 16px).          |
| **Align**     | Left, Center, Right. Default: Left.                        |
| **Color**     | Default (regular text) or Muted (lower-emphasis grey).     |
| **Max Width** | Optional CSS width constraint to keep long lines readable. |

## How it works

Text renders as a paragraph block with the configured size, alignment, and colour.

The **Muted** colour uses a grey from the theme palette (designed to be readable but lower-emphasis than headings or default text). Useful for captions, footnotes, and contextual notes.

{% hint style="info" %}
For long-form text, set a **Max Width** (e.g. `680px`). Lines that span the full page width are harder to read — narrower paragraphs improve scannability.
{% endhint %}

## Examples

**Welcome description.** Heading "Welcome back" + Text "Here's what's happened in your store today." Size M, Colour default.

**Form instructions.** A Text block above an Order Lines block, colour Muted: "Scan items or search by SKU below to add them to the order."

**Footer note.** Text at the bottom of a page, size S, colour Muted, alignment Center: "Need help? Contact your administrator."

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Heading</strong></td><td>For titles and section headers.</td><td><a href="/pages/VvEaZOjUkkdQtdqLi1Lo">/pages/VvEaZOjUkkdQtdqLi1Lo</a></td></tr><tr><td><strong>Card</strong></td><td>For grouped text with optional title.</td><td><a href="/pages/CL25ytWkdJL9JVqPKkg2">/pages/CL25ytWkdJL9JVqPKkg2</a></td></tr><tr><td><strong>Hero</strong></td><td>For big intro sections with text + button.</td><td><a href="/pages/oLF0GvowbgafCiW5QGv6">/pages/oLF0GvowbgafCiW5QGv6</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/content-components/text.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
