> 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/object-general-settings.md).

# Object General Settings

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

**Purpose**: Explains how to configure an object’s General Settings, including its identity, workflow behavior, display, search, and platform participation.
{% endhint %}

## Overview

General Settings define the core identity, behavior, and visibility of an <code class="expression">space.vars.object</code>. These settings determine how the object is named, displayed, searched, and where it appears across the platform.

Most settings can be updated after creation. Some settings are immutable and should be configured carefully.

During <code class="expression">space.vars.object</code> configuration, General Settings appears as Step 1:

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

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

***

## Object Identity Fields

<code class="expression">space.vars.object</code> identity fields define how the <code class="expression">space.vars.object</code> is labeled in the UI and referenced internally.

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

* **Object Name (required):** The plural, user-facing name of the <code class="expression">space.vars.object</code>. This name appears in navigation, list views, and settings. *Example: `Orders`*
* **Entity Name (required):** The singular form of the <code class="expression">space.vars.object</code> name. Used when referring to an individual <code class="expression">space.vars.entity</code> and in system messaging. *Example: `Order`*
* **Object API Name:** The programmatic identifier used in API endpoints and <code class="expression">space.vars.automations</code>. It’s generated from the object name and can be changed via API, but doing so is discouraged because it may break integrations. This value remains consistent across businesses that share the same schema, unlike the object ID, which is unique per business.
* **Object ID:** A system-generated unique identifier for the <code class="expression">space.vars.object</code>. Read-only.

***

## Workflow and Filtering

These settings control whether the <code class="expression">space.vars.object</code> behaves as a static data container or a lifecycle-driven workflow.

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

* **Contains Workflow:** Enables stage-based lifecycle behavior for the <code class="expression">space.vars.object</code>. When enabled, the <code class="expression">space.vars.object</code> becomes a workflow (pipeline) object that supports stages, lifecycle tracking, and related system fields. This setting is <mark style="color:$tint;">**immutable**</mark> after object creation, so enable it only for objects that must move through a defined process. For more information see, [Object Workflows](/docs/concepts/objects/object-configuration/object-workflows.md).
* **Enable Quick Filters:** Allows users to filter <code class="expression">space.vars.entities</code> in list views using predefined filters.
* **Display & Search:** Controls how <code class="expression">space.vars.entities</code> are labeled and discovered across the platform.
* **Display Name Template:** Controls how <code class="expression">space.vars.entities</code> are labeled and displayed throughout the UI.
  * Uses field placeholders (for example, `{{ name }}` or `{{ first_name }} {{ last_name }}`) to dynamically generate <code class="expression">space.vars.entity</code> labels
  * Useful when a single primary field isn’t enough to clearly identify a <code class="expression">space.vars.entity</code>
  * Helps improve clarity in lists, lookups, and relationship fields
  * The Display Name field is not shown by default for most <code class="expression">space.vars.objects</code>, since a standard primary field usually provides sufficient identification

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

* **Fields to Include in Search:** Specifies which fields are searched when users search for <code class="expression">space.vars.entities</code> of this <code class="expression">space.vars.object</code>. Include fields users are most likely to search by, such as names or identifiers.&#x20;

{% hint style="info" %}
**Note**: Only supported field types (for example, text-based or searchable identifier fields) can be included; non-searchable field types such as files, long-form content, or certain structured fields are excluded from search indexing.
{% endhint %}

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

***

## Description and Visuals

Description and Visuals define the <code class="expression">space.vars.object</code>’s purpose and establishes its visual identity across the platform to improve recognition and administrative clarity.

* **Object Description:** A short description of the <code class="expression">space.vars.object</code>’s purpose. This appears in settings and helps administrators understand how the object is intended to be used.

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

* **Default Color & Default Icon:** Define the <code class="expression">space.vars.object</code>'s visual identity across the platform. The default color appears in the toolbar and related <code class="expression">space.vars.object</code> blocks (and can be overridden in certain contexts), while the default icon provides a consistent visual marker in navigation and <code class="expression">space.vars.entity</code> views.

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

***

## Enabling Activities and Tracking Entity Value

Enabling Activities and Tracking Entity Value settings determine where the <code class="expression">space.vars.object</code> appears and which platform features it participates in.

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

* **Enable Activities:** Allows activities (such as tasks or logged actions) to be associated with <code class="expression">space.vars.entities</code> of this object. See [Activities](/docs/concepts/activities.md).&#x20;
* **Track Entity $ Value:** Enables value tracking for <code class="expression">space.vars.entities</code> of this object, allowing Kizen to calculate totals such as pipeline or commerce value.

***

## What's Next

After configuring your General Setting&#x73;**,** continue to [Object Workflows ](/docs/concepts/objects/object-configuration/object-workflows.md)to define lifecycle stages (if the object contains a workflow), or proceed to [Related Objects](/docs/concepts/objects/object-configuration/object-relationships.md) to connect this object to others in your data model.

<details>

<summary>Related Topics</summary>

* [Customize Object Fields](/docs/concepts/objects/object-configuration/customize-object-fields.md)
* [Object Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md)
* [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.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/object-general-settings.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.