# Object Core Concepts

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

**Purpose:** Explains the foundational architecture of <code class="expression">space.vars.objects</code> in <code class="expression">space.vars.Kizen\_company\_name</code>, including how schemas, fields, <code class="expression">space.vars.entities</code>, and relationships work together to support scalable data models, <code class="expression">space.vars.automation</code>, reporting, and integrations.
{% endhint %}

## Overview

<code class="expression">space.vars.objects</code> are the foundation of how all data is structured in the platform. They determine what fields are available, how <code class="expression">space.vars.entities</code> relate to one another, and which system behaviors are enabled. <code class="expression">space.vars.objects</code> provide the structure, fields define the details, and <code class="expression">space.vars.entities</code> store the actual data.

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

The <code class="expression">space.vars.Kizen\_company\_name</code> platform supports two <code class="expression">space.vars.object</code> configurations:&#x20;

* **Standard Objects**: used to model structured data for storage, reference, and organization.
* **Workflow Objects**: used to model process-driven data that moves through stages. They extend Standard <code class="expression">space.vars.object</code> behavior, adding stage management and optional pipeline reporting.

The platform remains flexible and can support a wide range of use cases beyond these common patterns. For example, a Standard <code class="expression">space.vars.object</code> can still track values without becoming a <code class="expression">space.vars.workflow</code>, and a <code class="expression">space.vars.workflow</code> can be used without enabling value tracking. This flexibility allows you to design data models that match your business needs while maintaining consistent behavior across <code class="expression">space.vars.automation</code>, reporting, and integrations.

### System Behaviors

The following behaviors describe how data is structured and behaves across the platform.

* **Objects contain the structure:** <code class="expression">space.vars.objects</code> function like a container that holds the schema, fields, relationships, and behavior for a type of data.
* **Fields define the structure:** Fields are configured on the <code class="expression">space.vars.object</code>, but Field values exist only on individual <code class="expression">space.vars.entities</code>.
* **Records contain the data:** <code class="expression">space.vars.entities</code> represent individual real-world items and store the actual data entered by users or integrations.
* **Relationships connect Records:** Relationships link <code class="expression">space.vars.entities</code> across <code class="expression">space.vars.objects</code> and enable navigation, <code class="expression">space.vars.automation</code>, and reporting.

For more information, see [Object Data Model](/docs/concepts/objects/object-data-model.md).

***

## Why Objects Matter

<code class="expression">space.vars.objects</code> form the structural foundation of the platform’s data model and directly determine how reliable reporting, <code class="expression">space.vars.automation</code>, integrations, and governance function at scale.

{% columns %}
{% column %}
A well-designed <code class="expression">space.vars.object</code> model enables:

* Accurate reporting and <code class="expression">space.vars.dashboards</code>
* Predictable <code class="expression">space.vars.automation</code> behavior
* Scalable integrations
* Clean data governance
* Reusable configuration across teams
  {% endcolumn %}

{% column %}
Poor <code class="expression">space.vars.object</code> design often leads to:

* Overly complex <code class="expression">space.vars.automations</code>
* Confusing <code class="expression">space.vars.entity</code> relationships
* Confusing end-user UX
* Reporting that cannot scale
* Redundant data
  {% endcolumn %}
  {% endcolumns %}

***

## Objects vs Contacts

<code class="expression">space.vars.contacts</code> are a specialized type of <code class="expression">space.vars.object</code> designed specifically for managing people. They behave like Standard <code class="expression">space.vars.objects</code> and represent a person and their data.

While fundamentally they behave similarly, there are a few key distinctions between them:

| Aspect                                                                                                                    | Contacts                                                                     | Custom Objects                                         |
| ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------ |
| Always present regardless of permissions                                                                                  | No                                                                           | No                                                     |
| Accessible via <code class="expression">space.vars.objects</code>/ <code class="expression">space.vars.entity</code> APIs | No                                                                           | Yes                                                    |
| Supports <code class="expression">space.vars.fields</code>                                                                | Yes                                                                          | Yes                                                    |
| Can relate to other <code class="expression">space.vars.objects</code>                                                    | Yes                                                                          | Yes                                                    |
| Schema flexibility                                                                                                        | Limited (<code class="expression">space.vars.workflows</code> not available) | Fully configurable                                     |
| Optimized for Communication, Email & SMS                                                                                  | Yes                                                                          | No                                                     |
| Unique Identifier                                                                                                         | Email                                                                        | <code class="expression">space.vars.entity</code> Name |

For more information, see [Contacts](/docs/concepts/objects/contacts.md).

***

## How Objects Are Used

<code class="expression">space.vars.objects</code> support many of the platform’s most powerful capabilities, including:

* **Workflows and lifecycle tracking:** Deals, onboarding flows, ticket lifecycles, project stages
* **Cross-Object Agentic Workflows:** Triggering <code class="expression">space.vars.entity</code> creation or updates in one object when another changes stage
* **Activity logging with cross-Record updates:** Logging an <code class="expression">space.vars.activity</code> on a <code class="expression">space.vars.contact</code> that updates fields on a related Ticket
* **Dashboards and reporting:** Aggregated metrics and insights based on <code class="expression">space.vars.object</code> fields and stages
* **API integrations:** External systems creating, updating, and relating <code class="expression">space.vars.entities</code> programmatically
* **Complex data modeling:** Supporting domains such as insurance, healthcare, and financial services

<code class="expression">space.vars.objects</code> provide the abstraction layer that makes all of this possible without hardcoding business logic.

### Object Configurations

<code class="expression">space.vars.objects</code> share the same foundation, but behave differently based on how they are configured. The configuration you choose affects how data flows through the system, how users interact with <code class="expression">space.vars.entities</code>, and how reporting and <code class="expression">space.vars.automation</code> behave.

#### Standard Configuration

Use when <code class="expression">space.vars.entities</code> represent structured data that does not move through stages.

* No stages or lifecycle
* Not shown in pipeline <code class="expression">space.vars.dashboards</code> or board views
* Supports fields, relationships, <code class="expression">space.vars.automations</code>, and APIs
* Common for reference or structured data (e.g., Locations, Policies, Assets, Providers)

#### Workflow Configuration

Use when <code class="expression">space.vars.entities</code> represent work that moves through a process or lifecycle.

* Includes stages and board (kanban) views
* Supports stage-based <code class="expression">space.vars.automation</code>
* Powers <code class="expression">space.vars.dashboards</code> and <code class="expression">space.vars.workflow</code> reporting
* Optional tracking for value and percent chance to close
* Common for Deals, Tickets, Applications, Projects, Cases, Reviews, and similar processes

### Choosing the Right Object Configuration

<table><thead><tr><th width="374">If your records...</th><th>Use this type</th></tr></thead><tbody><tr><td>Store structured data without lifecycle</td><td>Standard Configuration</td></tr><tr><td>Move through stages and require reporting on time in stage</td><td><code class="expression">space.vars.workflow</code> Configuration</td></tr><tr><td>Represent operational processes with heavy automation</td><td><code class="expression">space.vars.workflow</code> Configuration</td></tr><tr><td>Need to track monetary values</td><td>Standard or <code class="expression">space.vars.workflow</code> Configuration with <strong>Track Entity $ Value</strong> enabled</td></tr><tr><td>Track monetary values in a sales pipeline</td><td><code class="expression">space.vars.workflow</code> Configuration with <strong>Track Entity $ Value</strong> and <strong>Include % Chance to Close</strong> enabled</td></tr></tbody></table>

For more information on <code class="expression">space.vars.object</code> Configurations, see [Object Data Model](/docs/concepts/objects/object-core-concepts.md).

***

## Object Name vs Record Name

The platform distinguishes between <code class="expression">space.vars.object</code>-level labels (collection names) and <code class="expression">space.vars.entity</code>-level labels (instance names), each used in different UI and API contexts.

<code class="expression">space.vars.object</code> names are primarily used for navigation and structural labeling. <code class="expression">space.vars.entity</code> name fields are used to represent individual instances within an <code class="expression">space.vars.object</code>.

In addition to display labels, every <code class="expression">space.vars.entity</code> is assigned a system-generated backend name, which functions as the authoritative identifier for APIs, integrations, and internal references. Implementations should rely on this backend identifier rather than display labels.

<code class="expression">space.vars.objects</code> also have API names. For more information see [Object API Names](/docs/concepts/objects/object-apis/object-api-names.md).

***

## Key Use Cases

<code class="expression">space.vars.objects</code> support the following industry use cases:

### Industry Examples

{% tabs %}
{% tab title="Insurance" %}

#### Insurance Teams Modeling Policy and Operational Data

<code class="expression">space.vars.objects</code> provide the data foundation for insurance platforms by modeling real business entities such as policies, applications, claims, and accounts. This enables structured data capture, cross-<code class="expression">space.vars.object</code> relationships, reporting, and automation across the entire policy lifecycle.

Insurance teams use <code class="expression">space.vars.objects</code> to define consistent data models that support underwriting, servicing, compliance, renewals, and integration with external systems.

#### Examples include:

* Creating a Policy <code class="expression">space.vars.object</code> to store structured data such as policy number, coverage type, effective dates, carrier, premium amount, and status
* Defining an Application <code class="expression">space.vars.object</code> to track intake details, applicant information, risk attributes, and underwriting requirements
* Modeling a Claim <code class="expression">space.vars.object</code> with fields for loss type, incident date, adjuster assignment, reserve amounts, and claim status
* Using a Renewal <code class="expression">space.vars.object</code> with a workflow configuration to have stages such as Pending Review, Offered, Accepted, and Lapsed to manage retention workflows

#### How <code class="expression">space.vars.object</code>s Help:

* Establish a consistent, scalable data model for policies, applications, claims, and related <code class="expression">space.vars.entities</code>
* Enable relationships between <code class="expression">space.vars.entities</code>, such as linking a policy to a contact, agency, carrier, or claim
* Support lifecycle management using an <code class="expression">space.vars.object</code> with a <code class="expression">space.vars.workflow</code> configuration for renewals, onboarding, or claims processing
* Power reporting, <code class="expression">space.vars.dashboards</code>, and forecasting based on structured fields like premium value, status, and stage
* Enable <code class="expression">space.vars.automation</code> and integrations, such as creating renewal <code class="expression">space.vars.entities</code> when policies near expiration or syncing policy data to external policy administration systems via APIs and webhooks
  {% endtab %}

{% tab title="Healthcare" %}

#### Healthcare Teams Modeling Clinical and Operational Data

<code class="expression">space.vars.objects</code> provide the data foundation for healthcare <code class="expression">space.vars.workflows</code> by modeling real-world entities such as patients, referrals, appointments, care plans, and cases. This enables structured data capture, secure relationships between <code class="expression">space.vars.entities</code>, and scalable <code class="expression">space.vars.automation</code> across clinical and administrative processes.

Healthcare teams use <code class="expression">space.vars.objects</code> to define consistent data models that support care coordination, intake management, operational <code class="expression">space.vars.workflows</code>, and integration with external systems.

#### Examples include:

* Creating a Patient Intake <code class="expression">space.vars.object</code> to capture structured data such as demographics, referral source, insurance details, and consent status
* Defining a Referral <code class="expression">space.vars.object</code> to track referring provider, specialty, urgency level, and acceptance status
* Modeling an Appointment <code class="expression">space.vars.object</code> with fields for visit type, scheduled date, assigned provider, and attendance status
* Using a Care Pathway <code class="expression">space.vars.object</code> with a <code class="expression">space.vars.workflow</code> configuration to create stages such as Intake, Evaluation, Treatment, Follow-Up, and Completed

#### How Objects Help:

* Establish a consistent, scalable data model for clinical and operational <code class="expression">space.vars.entities</code>
* Enable relationships between <code class="expression">space.vars.entities</code>, such as linking patients to referrals, providers, appointments, and care plans
* Support lifecycle management using an <code class="expression">space.vars.object</code> with a <code class="expression">space.vars.workflow</code> configuration for referrals, treatment <code class="expression">space.vars.workflows</code>, and discharge processes
* Power reporting and <code class="expression">space.vars.dashboards</code> for operational visibility, such as referral volume, appointment throughput, and care outcomes
* Enable <code class="expression">space.vars.automation</code> and integrations, such as creating follow-up <code class="expression">space.vars.entities</code> when appointments are completed or synchronizing patient data with EHR systems through APIs and webhook events
  {% endtab %}

{% tab title="Financial Services" %}

#### Financial Services Teams Modeling Client and Financial Data

<code class="expression">space.vars.objects</code> provide the data foundation for financial services workflows by modeling real-world entities such as clients, accounts, opportunities, portfolios, and service cases. This enables structured data capture, relationship modeling, reporting, and <code class="expression">space.vars.automation</code> across advisory, banking, and operations functions.

Financial services teams use <code class="expression">space.vars.objects</code> to define consistent data models that support client onboarding, relationship management, compliance tracking, and lifecycle-based engagement.

#### Examples include:

* Creating a Client Profile <code class="expression">space.vars.object</code> to store structured data such as household details, risk tolerance, investment goals, and regulatory classifications
* Defining an Account <code class="expression">space.vars.object</code> to track account types, custodians, balances, and account status
* Modeling an Opportunity <code class="expression">space.vars.object</code> to manage advisory engagements with fields for estimated assets, probability to close, and expected close date
* Using a Client Lifecycle <code class="expression">space.vars.object</code> with a <code class="expression">space.vars.workflow</code> configuration to create stages such as Prospect, Onboarded, Active Client, Review Due, and At Risk

#### How Objects Help:

* Establish a consistent, scalable data model for clients, accounts, opportunities, and portfolios
* Enable relationships between <code class="expression">space.vars.entities</code>, such as linking clients to households, accounts, advisors, and service requests
* Support lifecycle management using an <code class="expression">space.vars.object</code> with a <code class="expression">space.vars.workflow</code> configuration for onboarding, engagement management, and retention <code class="expression">space.vars.workflows</code>
* Power dashboards and reporting for visibility into AUM, pipeline value, client segmentation, and service performance
* Enable <code class="expression">space.vars.automation</code> and integrations, such as creating onboarding <code class="expression">space.vars.entities</code> when a client is won or synchronizing client and account data with CRMs, custodial platforms, and external financial systems through APIs and webhook events
  {% endtab %}
  {% endtabs %}

***

## What's Next

Learn more about working with [Records](/docs/concepts/objects/records.md), then explore [Custom Fields](/docs/concepts/objects/custom-fields.md) to extend <code class="expression">space.vars.object</code> schemas and [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md) to manage access.

<details>

<summary>Related Topics</summary>

* [Object Data Model](/docs/concepts/objects/object-data-model.md)
* [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md)
* [Object Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md)
* [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md)
* [Object APIs](/docs/concepts/objects/object-apis.md)

</details>


---

# Agent Instructions: 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:

```
GET https://developer.kizen.com/docs/concepts/objects/object-core-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.