> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/using-the-template-preview.md).

# Using the Template Preview

The **Layout Builder** preview lets you inspect the arrangement of groups, fields and tables while editing an existing layout.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-51b135bdc643ceb48c7d0b7801cc4804c9c8a1eb%2Fs150-origin_layout_1.png?alt=media" alt="Template preview in the English Layout Builder."><figcaption><p>Template preview in the English Layout Builder.</p></figcaption></figure>

Open the intended document type and existing layout. Use **Elements** to inspect the available groups and controls. Click a field in the preview to open its **Properties**. Check labels, widths and visibility, then review how neighboring fields fit together.

Use the origin selector to inspect the configured origin context. Configured origin names remain unchanged when the interface language changes. The example shows an existing layout; it does not demonstrate a newly saved layout or a successful application to other origins.

Save only the intended changes and verify the resulting document view. See [Configuring field properties](/administration-and-setup/settings/global-settings/document-types/layout-manager/configuring-field-properties.md) and [Layouts and selection rules](/administration-and-setup/settings/global-settings/document-types/layout-manager/layout-selection-rules.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/using-the-template-preview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.