--- title: "Fields" description: "Add your own fields to Requiply and control where they appear: which fields exist, which records they apply to, which table columns show, and which detail rows show." canonical_url: "https://requiply.com/docs/en/guides/settings/fields" --- # Fields > Add your own fields to Requiply and control where they appear: which fields exist, which records they apply to, which table columns show, and which detail rows show. The **Fields** section is where admins shape the data Requiply captures — which custom fields exist, which records they apply to, which columns appear in the main tables, and which rows appear on detail pages. It is the single place to extend and rearrange Requiply beyond its built-in fields, so the same data flows into forms, lists, detail pages, and reporting consistently across the organization. You'll find this section under **Settings → Fields**. **Admin only.** Every page in this section is gated by the `admin` middleware. Non-admin users do not see the section in the sidebar and cannot reach the routes directly. ## Why fields matter Requiply's standard fields cover the basics — names, dates, prices, quantities — but every rental business has its own data needs (preferred contact method, internal references, allergy notes, special instructions, deposit caps). The Fields section turns those needs into reusable, structured data: 1. **Define once** under [Entity fields](https://requiply.com/docs/en/guides/settings/fields/entity-fields) — choose a name and a type (Textbox, Textarea, Number, Select, Multiselect). 2. **Attach where it's needed** under [Level configurations](https://requiply.com/docs/en/guides/settings/fields/level-configurations) — pick which entity levels (Item, Item Group, Client, Booking) the field appears on, and in what order. For client and booking fields, also decide whether the field is **Required** and whether it is **shown at creation** on the booking form and the quick client dialog. 3. **Promote into tables** under [Table column layout](https://requiply.com/docs/en/guides/settings/fields/table-columns) — choose which built-in and custom columns are visible on the main lists, and in what order. 4. **Arrange the record** under [Detail page fields](https://requiply.com/docs/en/guides/settings/fields/detail-page-fields) — choose which built-in and custom rows are visible when a single record is opened, and in what order. Each field has a stable **field key** generated from its name on creation, so the data stays addressable even if the display name is changed later in a UI sense. ## Pages in this section - [**Entity fields**](https://requiply.com/docs/en/guides/settings/fields/entity-fields) — the master list of custom fields for the organization. Add, edit, and delete fields with type-specific configuration (options for Select / Multiselect, format rules for Number, length rules for Textbox / Textarea). Name and field type are locked once a field has been created. - [**Level configurations**](https://requiply.com/docs/en/guides/settings/fields/level-configurations) — attach fields to entity levels and order them. Each level tab has **Add a field** chips, an ordered **Configured fields** list you can drag to reorder, and a live preview of the form. On the **Client** and **Booking** tabs each field also has **Required** and **Show at creation** switches. - [**Table column layout**](https://requiply.com/docs/en/guides/settings/fields/table-columns) — choose which columns are visible in the main tables for each entity level. Both built-in system columns and the organization's custom fields show up here, so business-specific data can be promoted into the visible columns of the Items, Item Groups, Clients, and Bookings lists. - [**Detail page fields**](https://requiply.com/docs/en/guides/settings/fields/detail-page-fields) — choose which rows are visible, and in what order, when a single item, item group, client, or booking is opened. System rows and custom fields are ordered together in one list, so a custom field can sit anywhere among the built-in rows instead of at the bottom of the card. ## Which entities support custom fields Custom fields can be attached to four entity levels: - **Item** — individual rentable units. - **Item Group** — the parent record that units belong to. - **Client** — customer records. - **Booking** — bookings. Each level has its own configuration on [Level configurations](https://requiply.com/docs/en/guides/settings/fields/level-configurations), [Table column layout](https://requiply.com/docs/en/guides/settings/fields/table-columns), and [Detail page fields](https://requiply.com/docs/en/guides/settings/fields/detail-page-fields) — switching tabs updates the URL with a `?tab=` query so a specific level can be linked to or refreshed without losing context. The **Organization** level appears only on Level configurations, because organizations have neither a table nor a detail page. Every one of the three layout pages shows a live **Preview** next to its pick list, rendering the form, table, or detail rows with sample data as you drag — so you can judge a layout before saving it. ## How this section connects to the rest of Requiply
Feature How fields interact with it
Inventory Item and Item Group level fields surface on the add-item form and on the Items / Item Groups tables.
Clients Client level fields appear on the add or edit client form and on the Clients table.
Booking Booking level fields appear on the booking form, on the Bookings table, and on the booking's detail page.
Detail pages Item, item group, client, and booking pages render the rows configured on Detail page fields , and offer a search box that filters those rows by label and value.
Stable field keys The auto-generated fieldKey is the durable identifier used to reference custom data, so it should be considered the durable handle for integrations or reporting even when the display name changes.
Type-specific behavior Format rules (min / max, fraction digits) and Select / Multiselect options chosen on Entity fields drive validation and selection behavior wherever the field is rendered.
## Tips and cautions **Tip:** Define a field on [Entity fields](https://requiply.com/docs/en/guides/settings/fields/entity-fields) first, then attach it to the levels you need on [Level configurations](https://requiply.com/docs/en/guides/settings/fields/level-configurations), and finally decide where it should be visible — as a column on [Table column layout](https://requiply.com/docs/en/guides/settings/fields/table-columns), as a row on [Detail page fields](https://requiply.com/docs/en/guides/settings/fields/detail-page-fields), or both. Skipping the middle step is the most common reason a newly added field doesn't show up on a form. **A new custom field starts out visible on detail pages but hidden from tables.** Detail pages show every field configured for the level, matching how they behaved before they became configurable; table columns wait in *Available Columns* until you promote them, and only offer fields with **Available for table view** switched on. **Heads up:** A field's name and type are locked once it's saved. If you need a different name or a different type, delete the field and create a new one — but be aware that deleting removes the field everywhere it was attached. ## Sitemap See the full [sitemap](https://requiply.com/docs/sitemap.md) for all pages.