# Reports in Kizen | Kizen Basics

## Overview

<code class="expression">space.vars.dashboards</code> provide a visual way to monitor activity, performance, and operational data in <code class="expression">space.vars.Kizen\_company\_name</code>. By combining charts, tables, and <code class="expression">space.vars.activity</code> views into a single workspace, <code class="expression">space.vars.dashboards</code> allow teams to track important information without navigating through multiple <code class="expression">space.vars.entities</code> or pages.

In this walkthrough, you will build a <code class="expression">space.vars.dashboard</code> for <code class="expression">space.vars.Theme\_park\_name</code> that displays scheduled <code class="expression">space.vars.activities</code> and guest information. You will create a <code class="expression">space.vars.dashboard</code>, add dashlets, and configure views that help park staff track upcoming guest events, monitor reservations, and quickly view customer data established in previous tutorials.

### Why This Matters

<code class="expression">space.vars.dashboards</code> help organizations turn operational data into actionable insight. Using <code class="expression">space.vars.dashboards</code> allows teams to:

* Monitor scheduled <code class="expression">space.vars.activities</code> and upcoming work
* Track <code class="expression">space.vars.entity</code> data such as <code class="expression">space.vars.contacts</code>, reservations, and guest information
* Identify operational issues quickly
* Share a common view of key business metrics across teams
* Reduce time spent navigating between individual <code class="expression">space.vars.entities</code>

For <code class="expression">space.vars.Theme\_park\_name</code>, the <code class="expression">space.vars.dashboard</code> ensures staff can easily monitor upcoming guest <code class="expression">space.vars.activities</code> and quickly access related <code class="expression">space.vars.contact</code> information. Instead of manually reviewing individual <code class="expression">space.vars.entities</code>, the team can see operational status in one place.

### Before You Begin

To build a <code class="expression">space.vars.dashboard</code>, you must:

* Be an Admin or Technical Builder with <code class="expression">space.vars.dashboard</code> creation permissions
* 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)
  * [Create Your First Record](/docs/kizen-basics/kizen-in-action/create-your-first-record-or-kizen-basics.md)
  * [Create Your First Workflow Object](/docs/kizen-basics/kizen-in-action/create-your-first-workflow-or-kizen-in-action.md)
  * [Schedule Your First Activity](/docs/kizen-basics/kizen-in-action/scheduling-your-activity-and-timelines-or-kizen-in-action.md)&#x20;
  * [Log Your First Activity](/docs/kizen-basics/kizen-in-action/tracking-your-activity-in-timelines-or-kizen-in-action.md)
* You should already have:
  * <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> for Marcus, Elena, Sofia, and Caleb
  * Ticket, Concession, and Ride Waiver <code class="expression">space.vars.objects</code> and <code class="expression">space.vars.entities</code> with associations to your <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>.
  * Scheduled and Logged Activities linked to tickets or various guest experiences

***

## Building a Dashboard

{% stepper %}
{% step %}

#### Navigate to **Dashboard**

In the navigation menu, select **Dashboard**.

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

Then select **ADD DASHBOARD** from the dropdown menu.
{% endstep %}

{% step %}

#### Set your Dashboard preferences

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

In the Add <code class="expression">space.vars.dashboard</code> modal, enter the following:

* **Dashboard Name:** Flywheel Operations <code class="expression">space.vars.dashboard</code>
* **Make Private:** Disabled

{% hint style="info" %}
**Note:** When **Make Private** is enabled, the <code class="expression">space.vars.dashboard</code> is hidden from search and other users cannot request access. Access must be granted manually.
{% endhint %}

* **Customize Styles:** Disabled

{% hint style="info" %}
**Note:** When **Customize Styles** is enabled, you can adjust the <code class="expression">space.vars.dashboard</code>’s visual appearance, including chart colors, trend lines, donut segments, headers, and other theme elements.
{% endhint %}

* **Sharing settings:**&#x20;
  * **All Team Members:** View
  * **Specific Roles:** Blank
  * **Specific Team Members:** Blank

{% hint style="info" %}
**Note:** **Share Settings** allow you to grant <code class="expression">space.vars.dashboard</code> access to specific team members, roles, or groups. For this tutorial, all team members have been given **view access** to the **Flywheel Operations Dashboard**.
{% endhint %}

Select **SAVE**

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

Your new <code class="expression">space.vars.dashboard</code> has been created.
{% endstep %}

{% step %}

#### Add an Activity Dashlet

Select **ADD DASHLET**

Enter the following:

* **Area:** Activities
* **Report Type:** Number of Activity Submissions
* **Choose Activity:** Ride Waiver Confirmation

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

For Values & Constraints, enter the following:

* **Dashlet Filters:** 0 Selected
* **Assigned to Employee with Role:** *Blank*
* **Assigned to Employee:** *Blank*

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

For Display Settings, enter the following:

* **Display Setting:** Trend
* **Datapoint Frequency:** Weekly
* **Name Your Dashlet**: Ride Waiver Confirmation - Total Submissions Over Time

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

Select **ADD.**&#x20;
{% endstep %}
{% endstepper %}

Now you have created a dashlet to allow <code class="expression">space.vars.Theme\_park\_name</code> staff to monitor all Ride Waiver submissions. Because Marcus has submitted those ride waiver confirmations before for his kids, your graph will look like this (with different dates):

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

Your <code class="expression">space.vars.Theme\_park\_name</code> Operations Dashboard is now ready for use.

***

## Apply What You've Learned

With the Waiver Submissions Dashlet now complete, it’s time to apply what you have learned to create a graph for tracking ticket purchases 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.

* **Area:** Activities
* **Report Type:** Number of Activity Submissions
* **Choose Activity:** Purchase Tickets
* **Dashlet Filters:** 0 Selected
* **Assigned to Employee with Role:** *Blank*
* **Assigned to Employee:** *Blank*

When you complete this process, you should have two graphs that look like this (with different dates).

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

***

## How This Fits Into Agentic Workflows

<code class="expression">space.vars.dashboards</code> do more than display data. They surface the results of <code class="expression">space.vars.automations</code> across the platform.

In the <code class="expression">space.vars.Theme\_park\_name</code> example, when a guest books an adventure experience, several automated processes may occur. A <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> may be created or updated, an <code class="expression">space.vars.activity</code> may be scheduled for the reservation, and an <code class="expression">space.vars.automation</code> may send a confirmation email to the guest. Because these actions are connected to <code class="expression">space.vars.entities</code> and <code class="expression">space.vars.activities</code>, <code class="expression">space.vars.dashboards</code> can display the resulting data as it occurs.

When <code class="expression">space.vars.dashboards</code> reflect live operational data, teams can use them to:

* Monitor activities created by <code class="expression">space.vars.automations</code>
* Track <code class="expression">space.vars.entity</code> updates generated by automated processes
* Identify upcoming tasks that require staff attention
* Observe operational metrics produced by automated events

By surfacing this information in one place, <code class="expression">space.vars.dashboards</code> provide operational visibility. Instead of reviewing individual <code class="expression">space.vars.entities</code> or processes, teams can monitor <code class="expression">space.vars.automations</code> as they unfold and respond quickly when action is required.

***

## Dashboard Capabilities by Role

{% columns %}
{% column %}

#### Admins

* Configure which <code class="expression">space.vars.dashboards</code> are available to teams and departments
* Define sharing settings and visibility for <code class="expression">space.vars.dashboards</code> and dashlets
* Control permissions for who can create, edit, or view <code class="expression">space.vars.dashboards</code>
* Ensure <code class="expression">space.vars.dashboards</code> display the correct <code class="expression">space.vars.entity</code> data and <code class="expression">space.vars.activity</code> information
* Maintain consistency in how operational metrics and reports are presented across teams
  {% endcolumn %}

{% column %}

#### Technical Builders

* Configure dashlets to display <code class="expression">space.vars.entities</code>, <code class="expression">space.vars.activities</code>, and operational data
* Apply filters, views, and sorting logic to shape <code class="expression">space.vars.dashboard</code> reporting
* Use <code class="expression">space.vars.dashboards</code> to monitor data generated by <code class="expression">space.vars.automations</code>
* Ensure <code class="expression">space.vars.dashboards</code> reflect changes to <code class="expression">space.vars.objects</code>, fields, and relationships
* Use <code class="expression">space.vars.dashboard</code> data to support reporting, operational monitoring, and downstream processes
* Create <code class="expression">space.vars.dashboards</code> that can be shared with other team members in the business.
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back to Your Industry

In the <code class="expression">space.vars.Theme\_park\_name</code> example, the <code class="expression">space.vars.dashboard</code> provides a central place for staff to monitor scheduled guest activities and quickly view related <code class="expression">space.vars.contact</code> information. The same <code class="expression">space.vars.dashboard</code> pattern applies across industries where teams need visibility into operational work, upcoming tasks, and customer <code class="expression">space.vars.entities</code>.

{% tabs %}
{% tab title="Insurance" %}
Tracking scheduled guest activities in a <code class="expression">space.vars.dashboard</code> is similar to monitoring policy and service <code class="expression">space.vars.activities</code> in insurance.

For example:

* A <code class="expression">space.vars.dashboard</code> showing new policy applications awaiting review
* A <code class="expression">space.vars.dashboard</code> tracking claims processing activities and required follow-ups
* A <code class="expression">space.vars.dashboard</code> displaying scheduled agent outreach or client meetings
* A <code class="expression">space.vars.dashboard</code> highlighting upcoming policy renewal reminders

Just as <code class="expression">space.vars.Theme\_park\_name</code> staff monitor upcoming guest reservations, insurance teams use <code class="expression">space.vars.dashboards</code> to monitor policy <code class="expression">space.vars.activity</code> and ensure critical milestones are not missed.
{% endtab %}

{% tab title="Healthcare" %}
Healthcare organizations use <code class="expression">space.vars.dashboards</code> to maintain visibility into patient care coordination and operational workflows.

For example:

* A <code class="expression">space.vars.dashboard</code> showing scheduled patient appointments for the day
* A <code class="expression">space.vars.dashboard</code> tracking follow-up care activities after procedures
* A <code class="expression">space.vars.dashboard</code> monitoring insurance verification tasks before visits
* A <code class="expression">space.vars.dashboard</code> displaying care team workloads and patient assignments

Just as <code class="expression">space.vars.Theme\_park\_name</code> staff monitor guest experiences and reservations, healthcare teams monitor patient care activities and operational readiness.
{% endtab %}

{% tab title="Financial Services" %}
Financial services teams rely on <code class="expression">space.vars.dashboards</code> to track client engagement and advisory workflows.

For example:

* A <code class="expression">space.vars.dashboard</code> displaying new client onboarding activities
* A <code class="expression">space.vars.dashboard</code> tracking scheduled portfolio review meetings
* A <code class="expression">space.vars.dashboard</code> monitoring compliance follow-ups and documentation reviews
* A <code class="expression">space.vars.dashboard</code> showing the investment workflow and upcoming client interactions

Just as <code class="expression">space.vars.Theme\_park\_name</code> staff use <code class="expression">space.vars.dashboards</code> to track guest interactions and reservations, financial services teams use dashboards to maintain visibility into client relationships and advisory activities.
{% endtab %}
{% endtabs %}

Regardless of industry, dashboards provide a centralized view of operational activity, helping teams monitor work, manage customer relationships, and ensure important steps occur at the right time.

***

## Congratulations

You've completed <code class="expression">space.vars.Kizen\_company\_name</code> Basics and now have a working foundation in <code class="expression">space.vars.Kizen\_company\_name</code> and the core skills to start building for your own organization!

From here, you can explore the rest of the <code class="expression">space.vars.Kizen\_company\_name</code> documentation at your own pace. Concept topics go deeper on how individual features work, and additional guides cover more advanced configuration as your needs grow.


---

# 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/reporting-in-kizen-or-kizen-in-action.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.