# Single Tab Forms

When designing Smart Forms on the ONEWEB platform, **tab configuration** plays an important role in structuring user input and organizing content.\
App Designer supports two main tab configurations:

* **Normal Tab**
* **Two‑Layer Tab**

This section introduces **Single Tab Forms**, which are built using the **Normal Tab** configuration.

***

#### Normal Tab (Single‑Layer Form)

A **Normal Tab** is used to design Smart Forms with a **single tab layer**, making it suitable for **simple or moderately complex forms**.

Key characteristics of Normal Tab forms:

* All form content is presented within **one tab**
* Multiple **sections or modules** can be placed inside the same tab
* Layout can be structured using rows and columns
* Best suited for one‑page form designs where users do not need to switch contexts

Normal Tabs help keep the user experience **simple, focused, and easy to navigate**, especially for straightforward data entry scenarios.

***

#### When to Use a Normal Tab

Use a Normal Tab when:

* The form can be completed within a **single screen**
* Data entry flow is simple and linear
* Users should not be distracted by multiple tab levels
* Content grouping can be handled using modules instead of tabs

This pattern is commonly used for:

* Basic registration forms
* Request or submission forms
* Master data maintenance screens

***

#### Example: Normal Tab Layout

Below is an example of a Smart Form designed using a **Normal Tab**, containing multiple modules within a single tab:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FGbGWq3TeYk14hNoDizFf%2Fimage.png?alt=media&#x26;token=41900c0a-0887-4b8c-9843-408dba167bc0" alt=""><figcaption></figcaption></figure>

***

{% hint style="info" %}
**Note:** For a complete list of Normal Tab configuration properties and advanced settings, refer to the **Normal Tab** section in the\
<https://docs.oneweb.tech/oneweb/reference/app-designer-reference.>
{% endhint %}

***

#### Design Perspective

Within **Smart Form design best practices**:

* Prefer **Normal Tabs** for clarity and simplicity
* Use modules to group related fields instead of adding tabs unnecessarily
* Move to **Two‑Layer Tabs** only when form complexity increases significantly

Single Tab Forms provide a clean foundation and should be the **default choice** unless additional navigation layers are required.


---

# 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/building-apps/ui-page-designer/ux-ui-components/smart-forms/smart-form-patterns/single-tab-forms.md?ask=<question>
```

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.