# Normal Tab
A **Normal Tab** is used to design a Smart Form with a **single‑layer tab structure**.\
It is suitable for **simple or moderately complex forms**, where all sections can be organized within one main navigation level.
Normal Tab design enables users to include **multiple sections or modules** under the same tab without introducing nested (multi‑layer) navigation.
***
### Purpose of Normal Tab
Normal Tab is designed to:
* Create **simple, one‑page Smart Forms**
* Group multiple sections or modules under a single tab
* Reduce navigation complexity for end users
* Support forms that do not require hierarchical separation
This tab type is ideal when the form structure is straightforward and does not require nested categorization.
***
### Main Tab Concept
In a Normal Tab design:
* The **top‑level first tab** is always referred to as the **Main Tab**
* The Main Tab is **system‑defined**
* The **Tab Description** for the Main Tab defaults to **“Main”** and **cannot be edited**
* All sections and modules are placed within this Main Tab
***
### Normal Tab Configuration
The following tab configuration settings are available for a Normal Tab:
#### Normal Tab Properties
| Tab Item | Mandatory | Description |
| ------------------- | --------- | ------------------------------------------------------- |
| **Tab ID** | Yes | Unique identifier generated automatically by the system |
| **Tab Description** | Yes | Defaults to **Main** and cannot be modified |
| **Table Name** | Yes | User‑defined tab name based on business requirement |
| **TabType** | No | Reserved for internal or advanced configurations |
***
### Designing Forms with Normal Tab
Within a Normal Tab, users can:
* Add **Modules** (1‑1, 1‑Many, Reusing Modules)
* Arrange sections vertically within the tab
* Design logical groupings using modules instead of nested tabs
* Apply consistent layouts for better user experience
This approach keeps form navigation **flat and intuitive**.
***
### Example: Normal Tab Usage
The example below illustrates how a Normal Tab appears in both:
* **Facade Screen (End‑User View)**
* **Configuration Screen (App Designer)**
In this design:
* Users interact with a single tab
* All form elements are visible within one navigational context
* No nested or secondary tab navigation is required
***
### Usage Guidelines
* Use **Normal Tab** for simple or flat form structures
* Prefer modules over creating unnecessary tabs
* Keep Main Tab focused and well‑organized
* Avoid overcrowding the Main Tab with unrelated content
* Upgrade to **2‑Layer Tab** when structured separation is required
***
### Summary
The **Normal Tab** provides a clean and straightforward way to design Smart Forms with a **single‑layer navigation model**.
Key points:
* Supports one‑level tab navigation
* Main Tab is system‑defined and mandatory
* Ideal for simple and medium‑complexity forms
* Allows multiple modules within the same tab
* Improves usability by minimizing navigation complexity
Normal Tabs are best suited when simplicity and clarity are prioritized in Smart Form design.
---
# Agent Instructions: 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:
```
GET https://docs.onewebstack.com/designer-reference/app-designer/entity/create-new-entity/tabs/normal-tab.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.