> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/studio/admin-and-configuration/fields-and-record-layout-management.md).

# Fields and Record Layout Management

Origin Studio stores metadata as **Fields** on a Record.

Admins can define fields and control how they show in the UI.

### Fields

A **Field** is one piece of information on a Record.

Fields can be:

* **System fields**. Fabric-defined. Required for core operations.
* **Custom fields**. Tenant-defined. Built for your model.

Custom fields commonly include:

* Free text
* Single select / multi select
* List
* Boolean
* Date / time

Custom fields can be:

* Disabled, hidden, or deleted.
* Associated to one or more Work Types.
* Global or localized (multi-language values).

### Datasets

A **Dataset** is the allowed value set for a select field.

Datasets apply to:

* Select (Single)
* Select (Multiple)

Datasets can also be localized.

### Record layout: Data Groups and Sections

The UI organizes fields using:

* **Data Groups**: logical groupings (Identifiers, Contributors, Tags).
* **Sections**: field collections inside a Data Group.

Sections are the smallest unit for access control. Put sensitive fields into dedicated Sections.

### Validation and consistency

Field types apply built-in validation.

Datasets enforce allowed values for select fields.

### Video guides

{% embed url="<https://www.loom.com/share/9ced33b26554486182280596fa2999b3>" %}

{% embed url="<https://www.loom.com/share/5f34d0f039414d9a84e24e41a28a043f>" %}