Object Configuration

Configure Objects in Kizen by managing general settings, workflows, relationships, custom fields, layouts, and permissions to define how data is structured, connected, and displayed.

Overview

Object configuration defines how data is modeled, displayed, connected, and governed across the platform. Each Object is configured through a set of focused settings pages, each responsible for a specific aspect of Object behavior.

Configuration is modular. Changes in one area (such as fields or relationships) may affect other areas (such as layouts or APIs), but each setting is managed independently.

Why Object Configuration Matters

Object configuration determines how data behaves across the platform. The decisions you make shape how teams work, how reliably data moves through workflows, automations, and APIs, and how well the system scales as your business grows.

When Objects are configured well, they support:

• Consistent, trustworthy data that teams can rely on

• Clear, predictable workflows that reflect real-world processes

• Stable automations and integrations built on durable schemas

• Accurate reporting and analysis based on structured, connected data

• Clear ownership and governed access, reducing risk as teams expand

Poor or rushed configuration has the opposite effect. It leads to fragmented schemas, unclear ownership, brittle automations, and Records that are difficult to search, report on, or maintain. Over time, these issues compound, making changes more expensive and limiting what the platform can support.

Because Objects sit at the center of Records, workflows, permissions, and APIs, configuration decisions are foundational. Investing in thoughtful setup early reduces rework later and ensures Objects remain usable, extensible, and understandable as your system evolves.

---

Object Configuration Areas

Use the pages below to configure different aspects of an Object.

General Settings

Define the Object’s identity and core behavior, including naming, workflow eligibility, searchability, and platform participation.

See Object General Settings.

Workflows

Control whether the Object follows a lifecycle and configure stages, probabilities, and workflow behavior.

See Object Workflows.

Relationships

Define how the Object connects to other Objects and how Records reference each other. Relationships shape data visibility, navigation, and reporting.

See Object Relationships.

Custom Fields

Define the Object’s data schema by creating and managing fields. Fields control what data can be stored, validated, and exposed through APIs.

See Object Custom Fields.

Layout Customization

Control how fields and related data are arranged on Record pages and in list views. Layouts affect presentation only and do not change the underlying schema.

See Object Layout Customization.

Permissions

Control who can view, create, edit, and delete Records for this Object. Permissions apply across the UI and APIs.

See Object Permissions.

---

Configuration Recommendations

Object configuration should be managed through the UI rather than the API. While many settings can be retrieved programmatically, schema design and structural changes (such as fields, relationships, layouts, and permissions) should be configured directly in the application to ensure consistency, validation, and proper system behavior.

Although settings can technically be adjusted independently, the following order is recommended:

1. General Settings

2. Workflows (if applicable)

3. Relationships

4. Custom Fields

5. Layout Customization

6. Permissions

This sequence reflects a logical layering of functionality, as each step builds on foundational decisions made in the previous one.

---

What’s Next

Select a configuration area above to begin setting up your Object, or start with General Settings to define the Object’s core behavior.

Related Topics

• Object Core Concepts

• Object Data Model

• Object APIs