Customize Object Fields

Define and manage Object fields in Kizen, including field categories, field types, validation rules, and metadata, to control how data is stored, organized, and exposed.

Audience: Admins, Developers, Solution Architects

Purpose: Explains how to define and manage custom fields for an Object, including field categories, field types, and metadata, to control how data is stored, validated, and exposed across the platform.

Overview

Custom Object Fields define the Object’s data schema by specifying what information can be stored on each Record and how that information is organized. Fields are grouped into categories to improve clarity and support layout organization.

During Object configuration, Customize Fields appears as Step 3. If Workflows are enabled, it becomes Step 4.

1. General Settings

2. Related Objects

3. Customize Fields

4. Customize Layout

5. Permissions

To learn more about custom field types, see Custom Fields.

---

Field Categories

Categories act as logical groupings for fields and are used to structure layouts and Record 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.

---

Fields

Fields define individual data points stored on each Record.

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 Record can be created. For workflow Objects, required fields may also be enforced before a Record can move to another stage.

System-required fields cannot be removed.

---

Export Field Metadata

Exports the Object’s field configuration, including field names, IDs, types, and options.

Use this export when:

• Building API integrations

• Validating data mappings

• Auditing Object 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 Object 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.

1

Field Settings

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

• Field Name: The user-facing label for the field. Appears on Records, 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.

2

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 Records, workflows, and integrations.

3

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 Records

• The field can be added to layouts

• The field becomes part of the Object’s API schema

---

What’s Next

After configuring fields, continue to Customize Layout to control field placement on Record pages. You can also learn about Fields, or you can proceed to Permissions to define who can view or edit Records and fields.

Related Topics

• Object General Settings

• Object Workflows

• Object Relationships