> For the complete documentation index, see [llms.txt](https://docs.ezra360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezra360.com/overview/components-overview/forms/section.md). # Section **Sections** provide a clear structure of the forms in Ezra360, and these sections contains a set of forms and fields. **#1** Shows a section called "Banking Details". \ **#2** shows sections collapse or expand the display of information within a form, by clicking on the top right arrow on that section, this feature allows users to focus on the sections they need while hiding the rest of which is useful when dealing with forms that contain large number of fields.\ \ You will often find multiple sections within the form. Each section contains a set of fields that are logically related or pertain to a specific aspect of the entity being displayed. These sections are visually separated from each other to provide clarity and structure to the form.

Section Templates
1 Column	A tabbed interface where content is displayed in a single vertical column.
2 Columns with single heading	The tab layout features a horizontal arrangement of tabs, with two columns of content beneath each tab. The content is organized with a single heading for each tab, dividing the space into two sections for presenting information, data, or forms side by side.
2 Columns with 2 headings	Each tab has two sub-sections with separate headings. This configuration allows for more detailed segmentation of content, presenting two distinct sets of information under each tab.
3 Columns with single heading	The tab layout involves horizontal tabs, with three columns of content under each tab. A single heading accompanies each tab.
3 Columns with 3 headings	The tab layout features horizontal tabs, each with three sub-sections, each having its own heading.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ezra360.com/overview/components-overview/forms/section.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.