# Create Your First Record | Kizen Basics

## **Overview**

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

Now that you’ve created your <code class="expression">space.vars.objects</code>, it’s time to add your first <code class="expression">space.vars.entities</code> to them. In <code class="expression">space.vars.Kizen\_company\_name</code>, a [Record](/docs/concepts/objects/records.md) is a single entry of data inside an <code class="expression">space.vars.object</code>. It works similar to a row in a table, and stores all the information related to your <code class="expression">space.vars.object</code> grouping.&#x20;

For example, if your <code class="expression">space.vars.object</code> is a collection of ticket data, then a <code class="expression">space.vars.entity</code> would be all the data associated with one ticket or one purchase of tickets. The fields you define in your <code class="expression">space.vars.object</code> shape what data each Record contains.&#x20;

In this topic, we continue following the Reyes family on their first visit to <code class="expression">space.vars.Theme\_park\_name</code>. Your next step is to store Marcus’ Ticket purchase in the Tickets <code class="expression">space.vars.object</code>, then connect the ticket data back to the family's <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>. You will:

* Learn to create **Ticket** <code class="expression">space.vars.object</code> Data
* Learn how fields determine what data each <code class="expression">space.vars.entity</code> can hold
* See how <code class="expression">space.vars.entity</code> structure supports Workflows, Activities, <code class="expression">space.vars.automations</code>, and reporting
* Apply those same steps to create data for the **Concessions** <code class="expression">space.vars.object</code> and **Ride Waiver** <code class="expression">space.vars.object</code>

These <code class="expression">space.vars.entities</code> become the foundation for all operational processes in <code class="expression">space.vars.Theme\_park\_name</code> and in your own business use cases.

### **Why This Matters**

Well-structured <code class="expression">space.vars.entities</code> impact nearly everything in <code class="expression">space.vars.Kizen\_company\_name</code>, including:

* **Accuracy:** Clear fields prevent missing or duplicated data, for example, a dropdown for Stage Status ensures staff select *Searching* rather than typing it freehand.
* **Agentic Workflows:** <code class="expression">space.vars.workflows</code> depend on consistent field values to trigger correctly, such as sending a notification only when Stage Status changes to *Located.*
* **Reporting:** <code class="expression">space.vars.dashboards</code> and filters rely on clean, meaningful fields, a mislabeled stage can cause requests to disappear from operational reports.
* **Scalability:** Good <code class="expression">space.vars.entity</code> structure grows with your operations without requiring rebuilds as processes expand.
* **Activities:** Logged or scheduled tasks pull data directly from <code class="expression">space.vars.entities</code>, so a missing <code class="expression">space.vars.contact</code> field means staff can't follow up automatically.

When your <code class="expression">space.vars.entities</code> are organized correctly, <code class="expression">space.vars.workflows</code> run without errors and your operational data tells a trustworthy story.

***

## **Before You Begin**

To complete this task, you must:

* Have permissions to create and edit <code class="expression">space.vars.entities</code> on the <code class="expression">space.vars.objects</code> you are modifying.
* Have completed:
  * [Create Your First Contact Record](/docs/kizen-basics/kizen-in-action/create-your-first-contact-record-or-kizen-basics.md)
  * [Create Your First Object](/docs/kizen-basics/kizen-in-action/create-your-first-object-or-kizen-basics.md)
* You should also have three <code class="expression">space.vars.objects</code> already created:
  * **Tickets** for Marcus' purchase
  * **Concessions** for future food and snack purchases
  * **Ride Waivers** to capture permission forms the family must sign.
* You should also have <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> for all four family members

***

{% stepper %}
{% step %}

#### In the top navigation, select **Data** > **Custom Objects**

<div data-with-frame="true"><figure><img src="/files/MHcdATCf3tDttrSvu4rq" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select the **Tickets** Object

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

{% hint style="info" %}
**Note:** The table on the Tickets page will be empty because you haven’t added any <code class="expression">space.vars.entities</code> yet.
{% endhint %}
{% endstep %}

{% step %}

#### Create a new <code class="expression">space.vars.entity</code>

Select **NEW TICKET**

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

Enter the following:

* **Ticket Name:** Marcus Reyes - Flywheel Tickets
* **Owner:** Yourself
* **Ticket Value:** $42.99
* **Primary Contact:** Marcus Reyes
* **Visit Date:** 06/15
* **Number of Tickets:** 4
* **Admission Status:** Unused
* **Purchase Method:** Online

<div data-with-frame="true"><figure><img src="/files/tZWtj0QC6PagQ1JDRAiE" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select **SAVE**

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

You will now see the purchase for the tickets are saved in the <code class="expression">space.vars.object</code>.
{% endstep %}
{% endstepper %}

***

## **Apply What You’ve Learned**

Next, you’ll create a **Concession** <code class="expression">space.vars.entity</code> using the same steps you used for the **Ticket** <code class="expression">space.vars.entity</code> you set up earlier.

{% stepper %}
{% step %}

#### Navigate back to the **Objects** page

Select **BACK TO OBJECTS** to return to the <code class="expression">space.vars.objects</code> page.

<div data-with-frame="true"><figure><img src="/files/XQJt5T4WQbJPNsMWdQjv" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select the **Concessions** Object

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

Selecting the <code class="expression">space.vars.object</code> will navigate you to the Concession <code class="expression">space.vars.entities</code> page.
{% endstep %}

{% step %}

#### Enter your Record data

Select **NEW CONCESSION** and enter the following information.

* **Concession Name:** Popcorn
* **Owner:** Yourself
* **Concession Value:** $7.50
* **Primary Contact Record:** Sofia Reyes
* **Quantity:** 1
* **Purchase Date:** 6/15 at 2:30pm
  {% endstep %}

{% step %}

#### Now, enter data for 3 other concessions

The data for the next three concessions can be found in the expanders below.

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

<details>

<summary>Fried Dough</summary>

* **Concession Name:** Fried Dough
* **Owner:** Yourself
* **Concession Value:** $8.50
* **Primary Contact Record:** Sofia Reyes
* **Quantity:** 1
* **Purchase Date:** 6/15 at 2:30pm

</details>

<details>

<summary>Cotton Candy</summary>

* **Concession Name:** Cotton Candy
* **Owner:** Yourself
* **Concession Value:** $6.00
* **Primary Contact Record:** Caleb Reyes
* **Quantity:** 1
* **Purchase Date:** 6/15 at 2:30pm

</details>

<details>

<summary>Soda</summary>

* **Concession Name:** Soda
* **Owner:** Yourself
* **Concession Value:** $4.50
* **Primary Contact Record:** Caleb Reyes
* **Quantity:** 1
* **Purchase Date:** 6/15 at 2:30pm

</details>
{% endstep %}

{% step %}

#### Finally, Navigate to the **Ride Waiver** Object and create a Record

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

Enter the following Ride Waiver Record:

* **Ride Waiver Name:** Sofia Reyes Ride Waiver
* **Owner:** Yourself
* **Ride Name:** Thunder Loop
* **Guest Record:** Sofia Reyes
* **Waiver Date:** 6/15 at 10:00 am
* **Visit Date:** 6/15
* **Waiver Status:** Signed
* **Guardian Contact:** Marcus Reyes

{% endstep %}
{% endstepper %}

Your <code class="expression">space.vars.entity</code>s are now fully configured and connected.

***

## How Records Power Agentic Workflows

Well-structured <code class="expression">space.vars.entities</code> are the foundation of every <code class="expression">space.vars.workflow</code> and <code class="expression">space.vars.automation</code>. Now that your **Ticket, Concessions,** and **Ride Waiver** <code class="expression">space.vars.entities</code> exist, the system can begin connecting operational processes to the Reyes family’s visit.

These <code class="expression">space.vars.entities</code> can trigger automated actions such as:

* Sending Marcus a ticket purchase confirmation email
* Scheduling a reminder email the day before the family’s visit
* Logging concession purchases during the park visit
* Recording Sofia’s completed ride waiver for staff verification
* Updating <code class="expression">space.vars.timelines</code> and related <code class="expression">space.vars.entities</code> automatically as new activities occur

In the next lesson, you’ll build your first <code class="expression">space.vars.workflow</code>, using a Support Ticket <code class="expression">space.vars.entity</code> as the trigger event.

### **Record Capabilities by Role**

{% columns %}
{% column %}

#### **Admins**

* Create, edit, reorder, and delete fields
* Modify <code class="expression">space.vars.entity</code> layouts
* Configure relationships between <code class="expression">space.vars.objects</code>
* Manage permissions for <code class="expression">space.vars.entity</code> editing
  {% endcolumn %}

{% column %}

#### **Technical Builders**

* Use the <code class="expression">space.vars.entities</code> API to create, update, or retrieve <code class="expression">space.vars.entities</code> programmatically
* Build integrations using webhooks
* Map external data sources into <code class="expression">space.vars.objects</code>
* Create scalable schemas that support complex <code class="expression">space.vars.automations</code>
  {% endcolumn %}
  {% endcolumns %}

***

## Industry Applications

<code class="expression">space.vars.entities</code> aren’t just for theme parks. In other industries, the same concepts apply.

{% tabs %}
{% tab title="Insurance" %}
In insurance, <code class="expression">space.vars.entities</code> represent the individual entries stored within each <code class="expression">space.vars.object</code>. These <code class="expression">space.vars.entities</code> capture the specific details for applications, policies, claims, and other operational data used by insurers.

Common <code class="expression">space.vars.entities</code> include:

* Applications
* Policies
* Claims
* Insured items
* Beneficiaries

Industry parallels to the <code class="expression">space.vars.Theme\_park\_name</code> setup:

* **Guests Record** → Individual insured persons, dependents, or covered members
* **Ticket Record** → A policy or quote <code class="expression">space.vars.entity</code> created for a customer

These <code class="expression">space.vars.entities</code> allow insurers to:

* Track the details of individual applications, policies, and claims
* Capture information about insured assets or beneficiaries
* Maintain operational history for underwriting and servicing activities

Just as <code class="expression">space.vars.Theme\_park\_name</code> stores ticket purchases as <code class="expression">space.vars.entities</code>, insurance systems store applications, policies, and claims as <code class="expression">space.vars.entities</code> within their respective <code class="expression">space.vars.objects</code> to support business operations.
{% endtab %}

{% tab title="Healthcare" %}
In healthcare, <code class="expression">space.vars.entities</code> represent the individual entries stored within each <code class="expression">space.vars.object</code>. These <code class="expression">space.vars.entities</code> capture the details of patient interactions, clinical activities, and operational processes that occur throughout the care lifecycle.

Common <code class="expression">space.vars.entities</code> include:

* Appointments
* Visits or patient encounters
* Intake forms
* Care plans
* Orders or referrals

Industry parallels to the <code class="expression">space.vars.Theme\_park\_name</code> setup:

* **Guest Record** → A patient or individual receiving care
* **Ticket Record** → A visit or appointment <code class="expression">space.vars.entity</code> associated with that patient

These <code class="expression">space.vars.entities</code> allow healthcare organizations to:

* Track scheduled appointments and completed visits
* Capture patient intake information and care plans
* Manage referrals, orders, and follow-up care activities

Just as <code class="expression">space.vars.Theme\_park\_name</code> stores ticket purchases as <code class="expression">space.vars.entities</code>, healthcare systems store appointments, visits, and care activities as <code class="expression">space.vars.entities</code> within their respective <code class="expression">space.vars.objects</code> to manage patient care and operational <code class="expression">space.vars.workflows</code>.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, <code class="expression">space.vars.entities</code> represent the individual entries stored within each <code class="expression">space.vars.object</code>. These <code class="expression">space.vars.entities</code> capture the details of client accounts, financial transactions, and operational processes that occur across banking, lending, and investment services.

Common <code class="expression">space.vars.entities</code> include:

* Accounts
* Transactions
* Loan applications
* KYC (Know Your Customer) checks
* Investment portfolios

Industry parallels to the <code class="expression">space.vars.Theme\_park\_name</code> setup:

* **Guest Record** → A client or account holder
* **Ticket Record** → A loan application, account opening, or investment request associated with that client

These <code class="expression">space.vars.entities</code> allow financial institutions to:

* Track client accounts and financial activity
* Capture loan applications and verification details
* Maintain compliance <code class="expression">space.vars.entities</code> such as KYC documentation
* Manage investment portfolios and related transactions

Just as <code class="expression">space.vars.Theme\_park\_name</code> stores ticket purchases as <code class="expression">space.vars.entities</code>, financial systems store accounts, transactions, and applications as <code class="expression">space.vars.entities</code> within their respective <code class="expression">space.vars.objects</code> to support financial operations and regulatory compliance.
{% endtab %}
{% endtabs %}

***

## **What’s Next**

Now that you’ve created your first <code class="expression">space.vars.entity</code>s, the next step is learning how to build a <code class="expression">space.vars.workflow</code>. In [Create Your First Workflow](/docs/kizen-basics/kizen-in-action/create-your-first-workflow-or-kizen-in-action.md)**,** you’ll create a <code class="expression">space.vars.workflow</code> <code class="expression">space.vars.object</code> that tracks operational processes and moves records through defined stages.

For example, when Sofia realizes she left her backpack near one of the rides, park staff create a Lost Item Request that moves through stages such as *Reported*, *Searching*, and *Resolved*, ensuring the right staff members take action at each step.


---

# 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/kizen-basics/kizen-in-action/create-your-first-record-or-kizen-basics.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.