> 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.md).

# Layout Manager

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-4d6d1b4f216ba97a7fcea52901c84ae65d8328ab%2Flayout-manager-overview-en.png?alt=media" alt="Layouts and Selection Rules for the Invoice document type: the Layouts and Selection rules tabs with their counts, the Document Type chip, the Field Validation, Approval, Reject and Review screen tabs, the layout cards with their Custom badge and Edit, Clone and Delete actions, and the New layout button"><figcaption><p>The Layout Manager for the Invoice document type.</p></figcaption></figure>

The **Layout Manager** decides how a document type looks to the people who validate, approve, reject and review documents: which fields and groups appear on the screen, in which order, and how each field behaves. Every document type has its own layouts.

The page opens as **Layouts & Selection Rules**: layouts are reusable field arrangements, independent of the document origin, and rules decide which layout a document gets.

#### Screens and layout types

Validation, approval, reject and review are separate screens, and each of them has its own layouts, its own rules and its own default layout — an approval rule never changes the validation screen. Switch the screen with the **Field Validation**, **Approval**, **Reject** and **Review** tabs.

#### Layout cards

On the **Layouts** tab every layout of the selected screen is a card. A card shows the layout name, whether it belongs to your organisation (**Custom**) or is the **System default**, when it was last edited, and whether a selection rule targets it. **Edit** opens the layout in the Layout Builder, **Clone** copies it under a name you choose and **Delete** removes it — the system default can only be viewed, not changed or deleted. **New layout** asks for a name and opens the Layout Builder on the new, empty layout. The filter above the cards switches between **All**, **My layouts** and **System** layouts.

#### The Layout Builder

**Edit** opens the [Layout Builder](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/navigating-the-layout-manager.md):

* **Structure**, **Fields** and **Elements** on the left — the layout as a tree, every field of the document type with a counter of the fields already placed, and the groups and form elements you can drag onto the canvas.
* The **canvas** in the middle shows the layout as the user sees it. **Main layout** and **Table** switch between the page and a line-item table, **Document** opens the sample document beside it.
* The **Properties** panel on the right follows the selected element, with its settings grouped into **Display**, **Behaviour**, **Values & lists** and **Automation**. Groups and horizontal separators also have **Borders & spacing**.

**Save** in the header stores the layout. See [Save and Apply Changes](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/save-and-apply-changes.md) for the other header actions.

#### Which layout a document gets

The **Selection rules** tab of each screen holds the rules that pick the layout, and the **FALLBACK** row is the default layout used when no rule matches. See [Layout Selection Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/layout-selection-rules.md).

#### Related pages

* [Purpose and Use](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/purpose-and-use.md)
* [Navigating the Layout Builder](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/navigating-the-layout-manager.md)
* [Configuring Field Properties](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/configuring-field-properties.md)
* [Using the Template Preview](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/using-the-template-preview.md)
* [Save and Apply Changes](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/save-and-apply-changes.md)
* [Layout Selection Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/layout-selection-rules.md)
* [Best practices](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/best-practices.md)
* [Troubleshooting](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/troubleshooting.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.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.
