> 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/save-and-apply-changes.md). # Save and apply changes Changes made in the Layout Builder are not live until you save them. Saving stores the layout for the document type so that new documents use it. ## Saving your changes After you edit the layout, select **Save** in the header at the top right.

Layout Builder header with the layout selectors on the left and the Save button and More menu on the right — The **Save** button sits at the top right of the Layout Builder.

While you work, the header shows the state of your changes: * A **Save** button without a message next to it means the layout is unchanged. * **Unsaved changes** appears as soon as you modify the layout. Select **Save** to store the changes.

Layout Builder header showing the Unsaved changes indicator next to the Save button — The **Unsaved changes** indicator appears while the layout has not been saved yet.

After a successful save, the indicator is replaced by the time the layout was last saved. Selecting **Save** again is safe: if nothing has changed since the last save, nothing is written. If you try to leave the Layout Builder with unsaved changes, DocBits asks whether to discard them. Select **Cancel** to stay and save, or **OK** to leave without saving.

Dialog asking to confirm leaving the Layout Builder with unsaved changes — Confirmation shown when leaving with unsaved changes.

## Other header actions The **More** menu (three dots) next to **Save** holds the remaining layout actions: * **Auto generate template** — build a layout automatically from the fields of the document type. * **Apply Default layout to Origins** — copy the default layout to the layouts of the individual origins. * **Use default template** — reset the layout to the default template. * **Edit JSON** — edit the raw layout definition as JSON. * **Copy JSON** — copy the layout definition to the clipboard. * **Layout settings** — open the general layout settings.

Layout Builder More menu with Auto Generate template, Apply Default layout to Origins, Use default template, Edit JSON, Copy JSON and Layout settings — The actions available under the **More** menu.

## Applying the changes Once saved, the layout is used by the document processing workflow for that document type: * New documents processed with this document type use the updated layout. * Documents that were already processed keep the layout they were captured with. ## Testing the changes After saving, open a document of that document type and check that the fields and groups appear as intended. If something is missing, return to the Layout Builder, adjust the layout and save again. --- # 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/save-and-apply-changes.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.