> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/use/submission-layout/summary-layout.md).
# Summary Layout
The summary layout provides a dashboard-style overview of a submission.
The summary layout provides a dashboard-style overview of a submission, addressing four major needs.
* The need to display a summary of your submission on a single page. Ideal for longer forms.
* The need to display fields from child submissions without having to enter the child submission itself.
* The need to access, from a child submission, the parent submission that refers to it.
* The need to display metadata for your submission (creation date, user who created it, etc.)
{% hint style="info" %}
This page covers the summary layout as your users experience it. To build one for a form, read [Summary Layout](/user-documentation/build/building-forms/summary-layout.md) in the Build section.
{% endhint %}
## Use the summary layout
When a form has an active summary layout, opening a submission from that form will open the summary, as you have configured it.
To navigate to the standard view, a "View Details" button allows you to switch to the standard layout. The "Edit" button also navigates to the standard layout, but in "Edit" mode.
In relationship fields, clicking on the relation will open the submission in a new browser tab. If the related form also has a configured summary, this will open by default.
The summary layout is also available for mobile devices, and looks like this:
## Limitations
* The summary layout does not allow editing of the submission. It is a **read-only** view.
---
# 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://www.center.daxium-air.com/user-documentation/use/submission-layout/summary-layout.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.