> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables.md). # Add and edit data fields in your tables Data fields define what each record can store. In **Table view**, data fields appear as columns. In the form view, the same fields appear as form elements. This page covers **data fields**. It does not cover layout components used to design, structure, or control a form. {% hint style="info" %} You can add and edit fields in several places. No matter where you do it, you change the same underlying table structure. {% endhint %} ## **Where you can add and edit data fields** You can work with fields from the table, the form view, the right-side settings panel, the data model, or [**Ninox AI**](/builder-hub/ninox-ai/ninox-ai.md) **chat**. Choose the place that matches the task. ### **Add and edit data fields in the table** Use the table for quick structural changes while you review real records. This is the fastest place to add a field as a new column. Click **+** **Add column** in the table header to add another field directly from **Table view**. This opens a menu where you can add a **New data field**, add a calculated column, or add an existing linked field to the table view.

If you create a new data field, Ninox adds a new column to the table. You then choose the field name and field type.

### **Add and edit data fields in the form view** Use the form view when you want to work on fields where users insert data. To open the form view, click a field in a record in your table.\ Do not click a choice field for this. That opens the choice options, not the form view itself. Here, fields appear as form elements instead of columns. This is useful when you want to check labels, order, grouping, and form behavior.

Use **Quick settings** from the field toolbar to make fast changes to the selected field, such as the **Label**, **Internal name**, or **Required** setting. For **Single-choice** and **Multi-choice** fields, you can also edit **Options**.

You can also add a field from the end of the form view. Click **Add component**, then select **New data field**.

{% hint style="info" %} This also works in linked tables in the form view. Any field you add there changes the linked table itself. {% endhint %} ### **Add and edit data fields in the right-side settings panel** Use the right-side panel to access the full settings for a field. Click the gear in the top right to open the settings panel. You can also click **Open full settings** in **Quick settings** on the field toolbar in the form view.

You can work with fields from these areas: * **Add** tab under **Form** to browse available data fields and drag them to the form view in the right place * **Fields** tab under **Table** to review the field list, create a field, search, filter, and manage several fields together * **Settings** tab under **Form** to change the selected field in detail, including the label, internal name, default values, display settings, permissions, behavior, visibility, and automations {% hint style="info" %} The available settings depend on the selected field type. Different field types show different options. {% endhint %} ### **Add and edit data fields in the data model** Use the data model when you want to design the table structure more deliberately.\ This view helps when you work across several tables. It is especially useful for planning linked fields and checking how tables relate to each other. Access the data model from **Data model** in the **App navigation**. To add a field there, click **Create field** in the relevant table at the end of the list of existing fields.

### **Add and edit data fields with Ninox AI chat** You do not have to change every field manually. You can ask **Ninox AI chat** to add fields, change fields, or adjust the structure for you. This is useful when you already know the result you want and want Ninox to build it faster. When you are on the app screen, click **Ninox AI chat** in the left-side main navigation.

## **Field types and what they are for** Choose a field type based on the kind of data you need to store and how you want to use it later. Ninox groups data fields into these categories. * **Standard fields**\ Use standard fields for everyday values users enter directly.\ Examples include **Text**, **Multi-line text**, **Number**, **Yes/no**, **Single-choice**, **Multi-choice**, **File**, and **Logic**. * **Contact fields**\ Use contact fields for contact details and locations.\ Common examples are **Email**, **Phone**, **URL**, and **Location**. * **Date and time fields**\ Use date and time fields for schedules, deadlines, appointments, and durations.\ This group includes **Date**, **Date and time**, **Appointment**, **Time**, and **Duration**. * **Special fields**\ Use special fields for app-specific values that affect display or connect a record to a workspace user.\ Examples include **Rich text**, **Color**, **Icon**, **Signature**, and **User**. * **Relationship fields**\ Use relationship fields to connect records across tables.\ You will find **Link one record** and **Link many records** in the **Relationships** group, at the same level as **Data fields**. ### **Browse all data fields** Open [All data fields](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields.md) to see one page per field type. There you can open dedicated pages for: * standard fields * contact fields * date and time fields * special fields * relationship fields --- # 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables.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.