# Records

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

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

## Overview

<code class="expression">space.vars.entities</code> are the individual instances of business data managed within the platform. They represent the active information that teams create, update, relate, automate, and report on every day. Each <code class="expression">space.vars.entity</code> captures the data values associated with a specific business, such as a deal, asset, policy, or contact. When you interact with your data, you are interacting with <code class="expression">space.vars.entities</code>.

<code class="expression">space.vars.entities</code> power operational execution. They:

* Store business data
* Participate in <code class="expression">space.vars.automations</code>
* Support relationships between data
* Respect permission and access controls
* Serve as the foundation for reporting and integrations

While identifiers and required values may vary by <code class="expression">space.vars.object</code> type, the underlying concept remains consistent: a <code class="expression">space.vars.entity</code> is a single, manageable instance of structured business data.

***

## Records Mastery Checklist

Explore the following topics to understand how <code class="expression">space.vars.entities</code> function within the platform and support operational business data.

**Core Knowledge**

* [ ] What a record represents and when to use it **(Topic Coming Soon)**
* [ ] How records store and surface business data **(Topic Coming Soon)**
* [ ] How records differ from configuration artifacts like object schemas **(Topic Coming Soon)**

**Record Behavior**

* [ ] How record values are captured, updated, and archived **(Topic Coming Soon)**
* [ ] How records participate in Agentic Workflows **(Topic Coming Soon)**
* [ ] How record relationships connect data across objects **(Topic Coming Soon)**

**Access & Control**

* [ ] How permissions influence record visibility and editing rights **(Topic Coming Soon)**
* [ ] How team associations and interaction history affect access **(Topic Coming Soon)**
* [ ] How record-level access integrates with broader security models **(Topic Coming Soon)**

**Integration & APIs**

* [ ] How records are structured in API responses **(Topic Coming Soon)**
* [ ] How to retrieve, search, and update records via API **(Topic Coming Soon)**
* [ ] [How identifiers (such as record names or email) are resolved in lookup workflows](/docs/concepts/objects/records/records-apis/lookup-record-api.md)
* [ ] [How identifiers are used in upsert workflows](/docs/concepts/objects/records/records-apis/create-or-update-records-upsert-api.md)

***

## What’s Next

Continue to [Records Core Concepts](/docs/concepts/objects/records/records-core-concepts.md) to establish the foundational mental model required before configuring <code class="expression">space.vars.entities</code>, designing schema strategies, or working with APIs.

<details>

<summary>Related Topics</summary>

* [Objects](/docs/concepts/objects.md)
* [Custom Fields](/docs/concepts/objects/custom-fields.md)
* [Records Core Concepts](/docs/concepts/objects/records/records-core-concepts.md)&#x20;
* [Records Data Model](/docs/concepts/objects/records/records-data-model.md)
* [Records APIs](/docs/concepts/objects/records/records-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/records.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.