> 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/navigating-the-layout-manager.md).
# Navigating the Layout Manager
Use the **Layout Builder** to arrange the fields and groups that people see on a document. This guide uses the English **Invoice** layout in a sandbox organization.
## Open the Invoice layout
1. Go to **Settings → Document Types**.
2. Find **Invoice** and select **Layouts** on its card. The Layout Builder opens for that document type.
3. Check the layout selector at the top left. The example below shows **DEFAULT**.
Access document types from settings.
## Find groups and fields
The left **Elements** panel has three sections. **Groups** lists the document sections; the middle canvas shows their current arrangement. Select a field in the canvas and open **Properties** to change its display settings. See [Configuring Field Properties](/administration-and-setup/settings/global-settings/document-types/layout-manager/configuring-field-properties.md) for the available options.
Elements and groups in an existing layout.
Open **Fields** to find available document fields. Use its search box when the list is long, then drag the field into the desired group in the canvas. Fields already placed in the layout may appear unavailable in the list.
Available fields in the layout builder.
Open **Form Elements** for visual controls such as Text, Label, Check Box, separator, Button and Sub Group. Drag the element you need into the canvas, then check its **Properties**.
Form elements in the layout builder.
## Arrange and save
* Select a group title in the canvas to change its title. The **+** above the canvas adds a group; the adjacent braces icon opens the advanced JSON group form.
* Hover over a group for the copy-JSON, move-up, move-down, delete and drag-handle actions. To reorder fields, drag them within or between groups.
* Select a field in the canvas to open **Properties**. Its delete icon removes it from this layout. To configure validation, OCR or matching, use the separate [Fields settings](/administration-and-setup/settings/global-settings/document-types/fields/configuring-field-properties-1.md).
* Select **Save** in the top bar after editing. See [Save and Apply Changes](/administration-and-setup/settings/global-settings/document-types/layout-manager/save-and-apply-changes.md) before using the other top-bar actions, including template generation, default templates and applying a layout to origins.
---
# 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/navigating-the-layout-manager.md?ask=&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.
