> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/objects/object-configuration/customize-object-fields.md).

# Customize Object Fields

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Explains how to define and manage custom fields for an <code class="expression">space.vars.object</code>, including field categories, field types, and metadata, to control how data is stored, validated, and exposed across the platform.
{% endhint %}

## Overview

Custom <code class="expression">space.vars.object</code> Fields define the <code class="expression">space.vars.object</code>’s data schema by specifying what information can be stored on each <code class="expression">space.vars.entity</code> and how that information is organized. Fields are grouped into categories to improve clarity and support layout organization.

During <code class="expression">space.vars.object</code> configuration, Customize Fields appears as Step 3. If Workflows are enabled, it becomes Step 4.

1. General Settings
2. Related <code class="expression">space.vars.objects</code>
3. <mark style="color:$tint;">**Customize Fields**</mark>
4. Customize Layout
5. Permissions

To learn more about custom field types, see [Custom Fields](/docs/concepts/objects/custom-fields.md).

***

## Field Categories

Categories act as logical groupings for fields and are used to structure layouts and <code class="expression">space.vars.entity</code> views.

* Categories can be reordered
* Categories can be renamed or deleted
* Fields can be moved between categories

Use categories to group related data, such as order details, customer information, or fulfillment data. You can select **Add New Category** which creates a new field category.

<div data-with-frame="true"><figure><img src="/files/oYO2GhXmQdWPDxBEwza6" alt="" width="563"><figcaption></figcaption></figure></div>

***

## Fields

Fields define individual data points stored on each <code class="expression">space.vars.entity</code>.

Fields can be:

* Reordered within a category
* Moved between categories
* Edited to update labels or behavior
* Deleted (if not system-required)

Fields marked as required must contain a value before a <code class="expression">space.vars.entity</code> can be created. For workflow <code class="expression">space.vars.objects</code>, required fields may also be enforced before a <code class="expression">space.vars.entity</code> can move to another stage.

System-required fields cannot be removed.

***

## Export Field Metadata

Exports the <code class="expression">space.vars.object</code>’s field configuration, including field names, IDs, types, and options.

Use this export when:

* Building API integrations
* Validating data mappings
* Auditing <code class="expression">space.vars.object</code> schemas across environments

If selected, you'll receive an email with an option to download a custom field csv file.

***

## Add New Field

Use **Add New Field** to create a new field on the <code class="expression">space.vars.object</code> and define how data is captured, stored, and validated.

Adding a field is a two-step process:

1. Configure field settings
2. Choose a field type

Learn more about our [Custom Fields](/docs/concepts/objects/custom-fields.md).

{% stepper %}
{% step %}

### Field Settings

Field Settings define the field’s identity, organization, and descriptive metadata.

<div data-with-frame="true"><figure><img src="/files/kRqly1KtJxcczpkoagEU" alt="" width="563"><figcaption></figcaption></figure></div>

* **Field Name:** The user-facing label for the field. Appears on <code class="expression">space.vars.entity</code>s, layouts, and filters.
* **Category:** Determines which category the field belongs to.
* **Description:** Optional helper text explaining the purpose of the field.
* **Description Visibility:** Controls where the field description is displayed.

<div data-with-frame="true"><figure><img src="/files/eW7TJbG85Lcvrj1Y3xVB" alt="" width="370"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Choose Field Type

Field type determines how data is stored, validated, and displayed. Once created, a field’s type **cannot be changed**.

Choose the field type that best matches how the data will be used in <code class="expression">space.vars.entity</code>s, workflows, and integrations.

<div data-with-frame="true"><figure><img src="/files/VLcEenUD2HoXpUxKnJg7" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Saving the Field

Select **Save** to create the field and add it to the selected category. Select **Cancel** to discard changes.

Once saved:

* The field is available on <code class="expression">space.vars.entity</code>s
* The field can be added to layouts
* The field becomes part of the <code class="expression">space.vars.object</code>’s API schema
  {% endstep %}
  {% endstepper %}

***

## What’s Next

After configuring fields, continue to [Customize Layout](/docs/concepts/objects/object-configuration/object-layout-customization.md) to control field placement on <code class="expression">space.vars.entity</code> pages. You can also learn about [Fields](/docs/concepts/objects/custom-fields.md), or you can proceed to [Permissions](/docs/concepts/objects/object-configuration/object-permissions.md) to define who can view or edit <code class="expression">space.vars.entity</code>s and fields.

<details>

<summary>Related Topics</summary>

* [Object General Settings](/docs/concepts/objects/object-configuration/object-general-settings.md)
* [Object Workflows](/docs/concepts/objects/object-configuration/object-workflows.md)
* [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md)

</details>


---

# 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://developer.kizen.com/docs/concepts/objects/object-configuration/customize-object-fields.md?ask=<question>&goal=<endgoal>
```

`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.