# Create Your First Object | 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 %}

In <code class="expression">space.vars.Kizen\_company\_name</code>, an <code class="expression">space.vars.object</code> is like a table or a data container that you create to store and organize the data that matters to your business. <code class="expression">space.vars.objects</code> hold the <code class="expression">space.vars.entities</code> you’ll reference in <code class="expression">space.vars.automations</code>, <code class="expression">space.vars.dashboards</code>, and <code class="expression">space.vars.workflows</code>. <code class="expression">space.vars.contacts</code> store the people you need to communicate with, <code class="expression">space.vars.objects</code> store everything else — tickets, ride waivers, concessions, assets, tasks, memberships, and more.

In this walkthrough, you’ll create three <code class="expression">space.vars.objects</code> for <code class="expression">space.vars.Theme\_park\_name</code>:

* **Tickets Object:** to store ticket purchases and visitor passes, such as Marcus’s family admission
* **Concessions Object:** to capture food and merchandise purchases made during park visits
* **Ride Waiver Object:** to store and track ride waivers signed by guests

These <code class="expression">space.vars.objects</code> will become the foundation for your next steps, including creating <code class="expression">space.vars.entities</code> and building <code class="expression">space.vars.workflows</code> that automate communication, follow-up tasks, and daily park operations.

### Why This Matters

<code class="expression">space.vars.objects</code> define where your data lives and how it’s structured. Clear <code class="expression">space.vars.object</code> design prevents errors later, such as:

* <code class="expression">space.vars.workflows</code> not triggering correctly
* <code class="expression">space.vars.automations</code> missing required fields
* Reports failing to show accurate information
* Disorganized or duplicated data across your business

A well-planned <code class="expression">space.vars.object</code> gives your team a consistent, scalable data foundation. Now, lets start by creating your **Tickets** <code class="expression">space.vars.object</code>.

### Before You Begin

Before creating an <code class="expression">space.vars.object</code>, you must have the following:

* **Admin** permissions with the ability to create and edit <code class="expression">space.vars.entities</code>
* A Business workspace created

***

{% stepper %}
{% step %}

#### Navigate to **Objects**

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

1. In the top navigation, select **Data**.
2. Choose **Custom Objects**.

The Objects page opens with a default **Companies Object** already created. You won't need it for this walkthrough — feel free to delete it by selecting the ellipsis in the **Actions** column. If your real-world use case involves companies, keep it.
{% endstep %}

{% step %}

#### Select **NEW OBJECT**

The Reyes family includes four visitors. Earlier, you created <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> to store information about each member of the family.&#x20;

Now, you will create a **Tickets Object** to store ticket purchases made for park visits. This <code class="expression">space.vars.object</code> will define the structure used to capture purchases, such as who bought the tickets, how many were purchased, and the date of the visit.

{% hint style="info" %}
**Note:** In later steps, you will create Ticket <code class="expression">space.vars.entities</code> within this <code class="expression">space.vars.object</code> to track purchases like the one Marcus made for his family.
{% endhint %}

First, select the **NEW OBJECT** button. You will be taken to the General Settings page for your <code class="expression">space.vars.object</code>.
{% endstep %}

{% step %}

#### Fill out the **General Settings** page

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

For this example, you will enter the following:

* **Object Name:** Tickets

{% hint style="info" %}
**Note:** This is the name of the <code class="expression">space.vars.object</code> and represents the type of data you’re tracking. An <code class="expression">space.vars.object</code> is like a table or container, so this name describes the collection of <code class="expression">space.vars.entities</code> it will hold.
{% endhint %}

* **Record Name:** Ticket

{% hint style="info" %}
**Note:** This is the name you want to call an individual <code class="expression">space.vars.entity</code> in your <code class="expression">space.vars.object</code>. Remember, this is a specific <code class="expression">space.vars.entity</code> inside of your collection of data. Currently, this is called **Entity Name** in the UI.
{% endhint %}

* **Contains Workflow:** Disable

{% hint style="info" %}
**Note:** This feature is used for creating opportunity or deal pipelines and ticket workflows. We won’t use it in this example, but you’ll learn how it works in the [Create Your First Workflow](/docs/kizen-basics/kizen-in-action/create-your-first-workflow-or-kizen-in-action.md) topic.
{% endhint %}

* **Enable Quick Filters:** Disable
* **Object Description:** Stores <code class="expression">space.vars.entities</code> of ticket purchases made for park visits. This <code class="expression">space.vars.object</code> tracks details such as the purchaser, number of tickets, visit date, and other information related to admission.
* **Enable Activities:** Enabled
* **Track Track Entity $ Value:** Enabled
  {% endstep %}

{% step %}

#### Select **SAVE & CONTINUE**

This will automatically save your <code class="expression">space.vars.object</code> and take you to the Related <code class="expression">space.vars.objects</code> step below.

{% hint style="info" %}
**Note:** The Contacts relationship appears by default but isn't saved until you select **SAVE & CONTINUE.**
{% endhint %}

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

Next, we need to create a relationship between the Tickets Marcus purchased in the Tickets <code class="expression">space.vars.object</code> and his <code class="expression">space.vars.contact</code> information in the <code class="expression">space.vars.contacts</code> <code class="expression">space.vars.object</code> so we can keep track of who purchased what tickets.  To do this, under **Related Objects.**

Then enter the following:

* **Related Object:** Contacts
* **Relationship Type:** Many-to-One
* **Relationship Name:** Purchaser Contact
* **Reverse Relationship Name:** Related Ticket Records

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

Select **SAVE & CONTINUE**.
{% endstep %}

{% step %}

#### **Modify Step 3 Customize Fields**

Here is where you can [Customize your Object Fields](/docs/concepts/objects/custom-fields.md). The <code class="expression">space.vars.field</code> acts like a column in your table of data inside your <code class="expression">space.vars.object</code>. As you can see, when you created your <code class="expression">space.vars.object</code>, <code class="expression">space.vars.Kizen\_company\_name</code> automatically created table columns for you.

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

{% hint style="info" %}
**Note:** <code class="expression">space.vars.Kizen\_company\_name</code> automatically creates the **Ticket Name** field as the unique identifier for this <code class="expression">space.vars.object</code>.
{% endhint %}

Now, we will create new column data. Select **+ADD NEW FIELD** and create the following so we can properly capture your Ticket data. Add the following fields:

{% hint style="info" %}
**Note:** That you do not need to change the **Category** or **Description Visibility** settings for this example.
{% endhint %}

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

| Field Name            | Description                                               | Field Type                             | Field Purpose                                                                                         |
| --------------------- | --------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Visit Date**        | The date the tickets are valid for entry to the park.     | Date                                   | Tracks when the guest plans to visit the park.                                                        |
| **Number of Tickets** | The total number of tickets purchased in the transaction. | Number (Whole)                         | <code class="expression">space.vars.entities</code> how many admissions were purchased for the visit. |
| **Admission Status**  | Indicates whether the ticket has been used for entry.     | Dropdown. (Unused,Used)                | Tracks whether the ticket has been used or is still unused.                                           |
| **Purchase Method**   | Tracks how the tickets were purchased.                    | Dropdown (Online, In Person, Telephone | Identifies the source of the purchase, such as Online or In Person.                                   |

All new <code class="expression">space.vars.fields</code> should be visible in your Ticket info category including the relationship field you created in step 2.

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

Select **NEXT STEP** to continue.

{% hint style="info" %}
**Note:** You can use the **ADD NEW CATEGORY** feature to organize your <code class="expression">space.vars.fields</code> by category.
{% endhint %}
{% endstep %}

{% step %}

#### Select **Default Columns** tab from **Step 4 Customize Layout**

Here is where you can take the <code class="expression">space.vars.fields</code> you just created and then organize them on your Ticket Overview table.

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

Lets add the following fields we just created:

* Purchaser <code class="expression">space.vars.contact</code>
* Visit Date
* Number of Tickets
* Admission Status
* Purchase Method

Lets remove the columns we don't need that came standard with the Tickets <code class="expression">space.vars.object</code>.

* Owner
* Display Name
* Last Modified
  {% endstep %}

{% step %}

#### Select **SAVE & CLOSE**

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

Your Tickets <code class="expression">space.vars.object</code> is now ready to store <code class="expression">space.vars.entities</code> and support <code class="expression">space.vars.workflows</code> later in the walkthrough.
{% endstep %}
{% endstepper %}

***

## Apply What You've Learned

With the Tickets <code class="expression">space.vars.object</code> now complete, it’s time to apply what you have learned to create Concessions and Ride Waiver <code class="expression">space.vars.objects</code> using the same steps. These <code class="expression">space.vars.objects</code> will track purchases made in the park and adherence to safety policies.

Use the information below to set it up.

* **Object Name:** Concessions
* **Record (Entity) Name:** Concession
* **Enable Workflows:** Disable
* **Enable Quick Filters:** Disable
* **Object Description:** Stores records of concession purchases, including the product purchased, purchase date, visit date, and the Contact who made the purchase.
* **Enable Activities:** Enabled
* **Track Track Entity $ Value:** Enabled

#### Create Your Fields For The Concessions Object

{% hint style="info" %}
**Note:** For this example **do not** modify the Category or Description Visibility fields.
{% endhint %}

| Field Name                                | Description                                                                                                                                   | Field Type               | Field Purpose                                                                                                                                                  |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Concession Name** *(Unique Identifier)* | A unique name for the concession purchased                                                                                                    | Text (Unique Identifier) | Identifies the concession purchase <code class="expression">space.vars.entity</code> within the Concessions <code class="expression">space.vars.object</code>. |
| **Concession Value**                      | The total cost of the concession purchase.                                                                                                    | Currency                 | Tracks the revenue generated from the purchase.                                                                                                                |
| **Primary Contact**                       | The <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> of the person who made the purchase. | Relationship (Contacts)  | Links the concession purchase to the person responsible for the order.                                                                                         |
| **Purchase Date**                         | The date the concession item was purchased.                                                                                                   | Date/Time                | Tracks when the purchase occurred.                                                                                                                             |
| **Quantity**                              | The number of items purchased.                                                                                                                | Number (Whole)           | Captures how many units of the item were purchased.                                                                                                            |

#### Customize Your Default Columns

Now Navigate to **Customize Layout** > **Default Columns** and move your columns as follows

{% columns %}
{% column %}

#### Available Columns

Owner

Date Created

Display Name

Last Modified
{% endcolumn %}

{% column %}

#### Active Table Columns

Concession Name

Concession Value

Primary <code class="expression">space.vars.contact</code> Record

Purchase Date

Quantity

{% endcolumn %}
{% endcolumns %}

Select **SAVE & CONTINUE**, then **FINALIZE YOUR OBJECT** (you do not need to set permissions at this time). Now your **Concessions** <code class="expression">space.vars.object</code> is now ready for <code class="expression">space.vars.entity</code> creation and <code class="expression">space.vars.automation</code> triggers (such as sending confirmation messages or creating follow-up tasks)!

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

Now create one more new <code class="expression">space.vars.object</code> for ride waivers and use the information below to set it up.

* **Object Name:** Ride Waivers
* **Record (Entity) Name:** Ride Waiver
* **Enable Workflows:** Disable
* **Enable Quick Filters:** Disable
* **Object Description:** Stores <code class="expression">space.vars.entities</code> of ride waivers signed for park attractions, including the ride name, waiver date, visit date, and the <code class="expression">space.vars.contact</code> associated with the waiver.
* **Enable Activities:** Enabled
* **Track Track Entity $ Value:** Disabled

| Field Name                                 | Description                                                                                                                                               | Field Type                           | Field Purpose                                                                                                                                     |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Ride Waiver Name** *(Unique Identifier)* | A unique name for the waiver <code class="expression">space.vars.entity</code>.                                                                           | Text (Unique Identifier)             | Identifies the waiver <code class="expression">space.vars.entity</code> within the Ride Waiver <code class="expression">space.vars.object</code>. |
| **Guest Record**                           | The <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> of the guest who requires the waiver.            | Relationship: Contacts               | Links the waiver to the individual guest participating in the ride.                                                                               |
| **Ride Name**                              | The name of the ride requiring the waiver.                                                                                                                | Text                                 | Identifies which attraction the waiver applies to.                                                                                                |
| **Waiver Date**                            | The date the waiver was signed or approved.                                                                                                               | Date/Time                            | Tracks when the waiver was completed.                                                                                                             |
| **Visit Date**                             | The date of the park visit is associated with the waiver.                                                                                                 | Date                                 | Links the waiver to a specific park visit.                                                                                                        |
| **Waiver Status**                          | Indicates whether the waiver has been signed and approved.                                                                                                | Dropdown (Pending, Signed, Verified) | Tracks whether the guest has completed the required waiver.                                                                                       |
| **Guardian Contact**                       | The <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> of the parent or guardian who signed the waiver. | Relationship: Contacts               | Captures who approved the waiver if the guest is a minor.                                                                                         |

Ensure that you have customized your fields so only the ones shown above are visible!

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

***

## How This Fits Into Agentic Workflows

Now that <code class="expression">space.vars.Theme\_park\_name</code> has Tickets, Concessions, and Ride Waiver <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.Kizen\_company\_name</code> can begin connecting real processes to the Reyes family’s visit. Each <code class="expression">space.vars.object</code> captures a different part of the guest experience, from ticket purchases, to food purchases, to required ride permissions.

When Marcus’s Ticket <code class="expression">space.vars.entity</code> is created, it becomes the event that starts everything:

* A welcome email is sent
* Staff are assigned tasks
* Ride Waivers are sent out and wristbands are prepared
* A follow-up survey is scheduled

These <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> work best when the underlying <code class="expression">space.vars.objects</code> and <code class="expression">space.vars.entities</code> are structured correctly, which is why defining these <code class="expression">space.vars.objects</code> is an essential step before [Creating Your First Workflow](/docs/kizen-basics/kizen-in-action/create-your-first-workflow-or-kizen-in-action.md).

***

## Object Capabilities By Role

{% columns %}
{% column %}

#### **Admins**

* Create and manage <code class="expression">space.vars.objects</code>
* Add or modify fields
* Control permissions and relationships between <code class="expression">space.vars.object</code>
* Prepare data structures for <code class="expression">space.vars.workflows</code>, <code class="expression">space.vars.dashboards</code>, and <code class="expression">space.vars.automations</code>
  {% endcolumn %}

{% column %}

#### **Technical Builders**

* Integrate external systems using webhooks or ETL pipelines to populate <code class="expression">space.vars.object</code>
* Leverage <code class="expression">space.vars.entity</code>-level APIs to sync tickets and guest data from other platforms
* Build scalable data models with future <code class="expression">space.vars.automations</code> in mind
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

The three <code class="expression">space.vars.objects</code> you created for the Reyes family are specific to <code class="expression">space.vars.Theme\_park\_name</code>, but the same structure applies across many industries. <code class="expression">space.vars.objects</code> are how you model your business — they represent the data you track, the processes you automate, and the relationships your <code class="expression">space.vars.workflows</code> depend on.

Below are examples of how the concepts in this walkthrough translate into real-world use cases in Healthcare, Insurance, and Financial Services.

{% tabs %}
{% tab title="Insurance" %}
In insurance, <code class="expression">space.vars.objects</code> represent the structured data and processes that define underwriting, quoting, policy management, and claims.

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

* Applications
* Policies
* Vehicles, Properties, or Insured Assets
* Claims
* Beneficiaries
* Supporting Documents

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

* Tickets <code class="expression">space.vars.object</code> → Policy or Quote <code class="expression">space.vars.entities</code> linked to a <code class="expression">space.vars.contact</code> (applicant)
* Concessions <code class="expression">space.vars.object</code> → Transactions related to a policy, such as premium payments, service fees, or endorsements
* Ride Waivers <code class="expression">space.vars.object</code> → Signed disclosures, acknowledgments, or compliance documents required for coverage

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

* Trigger <code class="expression">space.vars.workflows</code> when an application is submitted
* Route tasks to underwriting or claims teams
* Generate policy documents
* Automate renewal reminders
* Track multi-step processes with full audit history

Just like <code class="expression">space.vars.Theme\_park\_name</code> uses Tickets to start visit <code class="expression">space.vars.workflows</code>, an Application or Claim <code class="expression">space.vars.object</code> can trigger <code class="expression">space.vars.automations</code> that route work through the appropriate teams.
{% endtab %}

{% tab title="Healthcare" %}
In healthcare, <code class="expression">space.vars.objects</code> often represent operational or clinical data that is not tied to direct communication. While a patient might exist as a <code class="expression">space.vars.contact</code>, much of the supporting information is better stored in <code class="expression">space.vars.objects</code> such as:

* Appointments
* Care Plans
* Intake Forms
* Encounters / Visits
* Orders, labs, or imaging requests
* Authorizations or referrals

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

* Tickets <code class="expression">space.vars.object</code> → Appointment or Visit <code class="expression">space.vars.entities</code> associated with a patient
* Concessions <code class="expression">space.vars.object</code> → Billing or charge <code class="expression">space.vars.entities</code> for services, medications, or procedures
* Ride Waivers <code class="expression">space.vars.object</code> → Consent forms, treatment authorizations, or liability waivers signed before care

<code class="expression">space.vars.objects</code> allow healthcare teams to:

* Track appointment details and provider assignments
* Run <code class="expression">space.vars.automations</code> for check-in <code class="expression">space.vars.workflows</code>
* Trigger tasks for pre-visit requirements (forms, documentation, prep)
* Schedule follow-up activities or compliance reminders

Just like Tickets trigger <code class="expression">space.vars.workflows</code> at <code class="expression">space.vars.Theme\_park\_name</code>, a Visit <code class="expression">space.vars.entity</code> can trigger automated pre-visit instructions, reminders, and post-visit follow-ups.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, <code class="expression">space.vars.objects</code> structure the core data that supports compliance, relationship management, and account operations.

Typical <code class="expression">space.vars.objects</code> include:

* Accounts
* Transactions
* Loan Applications
* Investments or Holdings
* KYC/AML Reviews
* Risk Profiles

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

* Tickets <code class="expression">space.vars.object</code>→ Account, loan, or investment application <code class="expression">space.vars.entities</code> tied to a client engagement
* Concessions <code class="expression">space.vars.object</code>→ Transaction <code class="expression">space.vars.entities</code> such as deposits, withdrawals, fees, or trade activity
* Ride Waivers <code class="expression">space.vars.object</code> → Signed disclosures, risk acknowledgments, or compliance documents required for financial services or investment activities

<code class="expression">space.vars.objects</code> help financial institutions:

* Run onboarding <code class="expression">space.vars.workflows</code> when a new account is created
* Validate required documentation
* Trigger advisor tasks
* Automate compliance reviews
* Track transaction-related activities

Just like Tickets drive visit preparation at <code class="expression">space.vars.Theme\_park\_name</code>, a Loan Application or New Account <code class="expression">space.vars.object</code> can drive automated review steps, outreach, reminders, and approval <code class="expression">space.vars.workflows</code>.
{% endtab %}
{% endtabs %}

***

## What’s Next?

Now that your Tickets, Concession, and Ride Waiver <code class="expression">space.vars.objects</code> are created, you’re ready to add real data to your workspace. In the next topic, [Create Your First Record](/docs/kizen-basics/kizen-in-action/create-your-first-record-or-kizen-basics.md), you’ll enter the following <code class="expression">space.vars.entities</code>:

* Marcus’s purchased ticket into the Tickets <code class="expression">space.vars.object</code>
* The Reyes family snack purchase in the Concessions <code class="expression">space.vars.object</code>
* Sofia’s ride waiver in the Ride Waiver <code class="expression">space.vars.object</code>

These <code class="expression">space.vars.entities</code> will prepare your workspace for building your first <code class="expression">space.vars.workflow</code>, where the system can trigger actions such as sending confirmations, creating tasks, or tracking guest activities.


---

# 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-object-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.