> 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/records/records-core-concepts.md).

# Records Core Concepts

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

**Purpose:** Explains how <code class="expression">space.vars.entities</code> function as the platform’s operational data layer, storing structured business data and enabling workflows, permissions, reporting, and API-driven integrations.
{% endhint %}

## Overview

<code class="expression">space.vars.entities</code> are the stored instances of business data that teams create, update, relate, and act upon within the platform. Each <code class="expression">space.vars.entity</code> holds the field data that represents a single deal, asset, policy, or contact. When users interact with the system, they are interacting with <code class="expression">space.vars.entities</code>.

A helpful analogy is a database table row. Each <code class="expression">space.vars.entity</code> represents a single row of stored data, containing the values that define one distinct <code class="expression">space.vars.entity</code>.

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

Workflows, permissions, reporting, and integrations frequently evaluate or modify <code class="expression">space.vars.entities</code>. Understanding how <code class="expression">space.vars.entities</code> behave is important when designing scalable data models and making informed architectural decisions.

### System Behaviors

The following behaviors describe how <code class="expression">space.vars.entities</code> operate across the platform:

* **Store field values:** Each <code class="expression">space.vars.entity</code> contains the data entered for a specific business entity. When values are created, updated, or cleared, the <code class="expression">space.vars.entity</code> reflects the current state while maintaining an auditable history of changes through system-managed timestamps and timeline activity.
* **Include system-managed attributes:** Every <code class="expression">space.vars.entity</code> contains system fields such as unique identifiers, created and modified timestamps, and ownership or association references. These ensure traceability and operational integrity.
* **Follow a defined lifecycle:** <code class="expression">space.vars.entities</code> are created, updated, related, automated upon, archived, and potentially unarchived. Archiving removes a <code class="expression">space.vars.entity</code> from active views while preserving history. Restoration reactivates it without data loss.
* **Generate timeline activity:** Changes create timeline entries that show what changed and who initiated the change, supporting governance and collaboration.
* **Enforce identifier constraints:** Each <code class="expression">space.vars.entity</code> must satisfy object-level uniqueness requirements to prevent duplication conflicts and maintain referential integrity.
* **Inherit visibility through associations:** Direct and indirect associations, evaluated alongside permissions, determine who can view or modify a <code class="expression">space.vars.entity</code>.

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

***

## Why Records Matter

<code class="expression">space.vars.entities</code> are the operational foundation of the platform’s data model and support core platform behaviors, including:

* Activate object schemas
* Power <code class="expression">space.vars.automations</code>
* Enable reporting and analytics
* Support permission models and governance
* Serve as the foundation for integrations and APIs

Poorly designed <code class="expression">space.vars.entity</code> strategies create downstream complexity. Thoughtful <code class="expression">space.vars.entity</code> design supports scalability, data integrity, and long-term maintainability.

***

## Object Records vs Contact Records

While <code class="expression">space.vars.object</code> <code class="expression">space.vars.entities</code> and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> behave consistently, there are several important distinctions:

| Aspect                                                                 | Object Records                                                            | Contact Records                                                       |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Foundational Record Model                                              | Yes                                                                       | Yes                                                                   |
| Supports Custom Fields                                                 | Yes                                                                       | Yes                                                                   |
| Participates in Relationships                                          | Yes                                                                       | Yes                                                                   |
| Participates in <code class="expression">space.vars.automations</code> | Yes                                                                       | Yes                                                                   |
| Primary Identifier                                                     | <code class="expression">space.vars.entity</code> Name                    | Email                                                                 |
| Minimum Data Requirements                                              | Defined by the <code class="expression">space.vars.object</code>'s Schema | At least one identifying field (such as name, email, or mobile phone) |
| Communication-Specific Behavior                                        | No                                                                        | Yes (subscriptions, messaging history, email status)                  |

Despite these differences, <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> remain <code class="expression">space.vars.entities</code> within the same underlying data model. They store values, participate in <code class="expression">space.vars.automations</code>, respect permissions, and support API operations in the same way as other <code class="expression">space.vars.object</code> <code class="expression">space.vars.entities</code>.

For deeper guidance specific to contact behavior and communication features, see [Contacts Core Concepts](/docs/concepts/objects/contacts/contacts-core-concepts.md).

***

## How Records Are Used

<code class="expression">space.vars.entities</code> are the data around which business processes are organized.

Common patterns include:

* Managing customers, deals, policies, assets, or projects
* Tracking lifecycle progression across defined stages
* Associating related data across <code class="expression">space.vars.objects</code>
* Triggering <code class="expression">space.vars.automation</code> based on <code class="expression">space.vars.entity</code> changes
* Supporting collaboration through shared visibility

***

## Key Use Cases

The <code class="expression">space.vars.entity</code> model supports diverse industries by enabling structured, operational data management around real-world entities. These examples illustrate the flexibility of the <code class="expression">space.vars.entity</code> model across industries. The underlying behavior remains consistent while adapting to specific business contexts.

### Industry Examples

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

#### Insurance Teams Managing Policy and Operational Records

<code class="expression">space.vars.entities</code> enable insurance platforms to manage policies, claims, applications, and related operational data as structured, traceable entities.

Insurance teams use <code class="expression">space.vars.entities</code> to capture lifecycle-driven data, associate related entities, and support compliance and servicing workflows.

Examples include:

* Creating Policy <code class="expression">space.vars.entities</code> to store structured data such as policy number, coverage type, effective dates, premium amount, and status
* Managing Claim <code class="expression">space.vars.entities</code> with loss details, incident dates, adjuster assignments, reserve amounts, and claim status
* Associating Policy <code class="expression">space.vars.entities</code> to agents, carriers, accounts, and related claims
* Tracking renewals through workflow-driven status progression

**How Records Help:**

* Maintain consistent operational data across policy lifecycles
* Enable structured relationships between policies, claims, agents, and accounts
* Support reporting and forecasting based on standardized field values
* Power automation such as renewal creation or claim escalation <code class="expression">space.vars.automations</code>
  {% endtab %}

{% tab title="Healthcare" %}

#### Healthcare Organizations Managing Patient and Care Records

<code class="expression">space.vars.entities</code> enable healthcare teams to organize patient data, care interactions, and provider relationships within a structured and governed framework.

Healthcare teams use <code class="expression">space.vars.entities</code> to maintain accurate engagement histories, manage lifecycle status, and coordinate care-related activities.

Examples include:

* Managing Patient <code class="expression">space.vars.entities</code> with identifying information, status, and care milestones
* Associating care interactions, providers, and treatment <code class="expression">space.vars.entities</code>
* Tracking engagement progression across intake, treatment, and follow-up stages

**How Records Help:**

* Centralize patient-related operational data
* Maintain traceable care history through timeline activity
* Support regulatory compliance through auditable patient record history and controlled data access
* Enable reporting across patient populations and care stages
  {% endtab %}

{% tab title="Financial Services" %}

#### Financial Services Teams Managing Client and Portfolio Records

<code class="expression">space.vars.entities</code> allow financial services organizations to manage client relationships, engagements, and portfolio activity in a structured, auditable format.

Financial teams use <code class="expression">space.vars.entities</code> to monitor lifecycle progression, enforce governance standards, and support advisor collaboration.

Examples include:

* Managing Client <code class="expression">space.vars.entities</code> with profile, engagement, and relationship data
* Associating advisors, portfolios, and related financial accounts
* Tracking milestones such as onboarding, review cycles, and compliance checkpoints

**How Records Help:**

* Establish structured client data models
* Support regulatory oversight through traceable record history and auditable field changes
* Enable relationship-driven reporting across accounts and advisors
* Power automation tied to engagement milestones or portfolio events
  {% endtab %}
  {% endtabs %}

***

## What’s Next

Continue to [Records Data Model](/docs/concepts/objects/records/records-data-model.md) to explore the architectural structure behind <code class="expression">space.vars.entity</code> storage and relationships or explore any of the topics below:

<details>

<summary>Related Topics</summary>

* [Records](/docs/concepts/objects/records.md)
* [Records Data Model](/docs/concepts/objects/records/records-data-model.md)&#x20;
* Team Interactions in Records **(Coming Soon)**
* Record Permissions **(Coming Soon)**
* [Records APIs](/docs/concepts/objects/records/records-apis.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:

```
GET https://developer.kizen.com/docs/concepts/objects/records/records-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.