# Prerequisites | Kizen Basics

## Overview

This page outlines the prerequisites required to complete the <code class="expression">space.vars.Kizen\_company\_name</code> Basics in Action walkthroughs. It explains the access, permissions, and environment setup you need before getting started so you can follow each example without interruption. Reviewing these requirements ahead of time helps ensure a smooth walkthrough experience as you move through the platform.

### Why This Matters

Confirming these prerequisites before starting helps prevent interruptions during the walkthrough. The examples in this guide require specific permissions and access to a Business workspace where you can safely create <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.activities</code>, and <code class="expression">space.vars.automations</code>.

Reviewing these requirements ensures that you:

* Have the correct permissions to complete each step
* Can create and modify data structures used in the examples
* Work in a safe environment that does not affect production data
* Move through the walkthrough without needing to stop for access changes

Preparing your environment ahead of time allows you to focus on learning how the platform works rather than troubleshooting setup issues.

***

## Before You Begin

Before beginning the <code class="expression">space.vars.Theme\_park\_name</code> walkthrough, you **do not need prior experience** with <code class="expression">space.vars.Kizen\_company\_name</code>. However, you must have the following:

* **A Kizen Account:** You’ll need access to your <code class="expression">space.vars.Kizen\_company\_name</code> [environment](https://go.kizen.com) so you can follow along and complete each step in the example.
* **Admin Permissions:** Ensure you are and administrator and have permission to:
  * View & Create <code class="expression">space.vars.objects</code>
  * Create or Modify <code class="expression">space.vars.activities</code>
  * Build <code class="expression">space.vars.automations</code>
  * Create a business workspace
  * Access business settings

{% hint style="info" %}
**Note:** If you don't have the correct permissions, ask your <code class="expression">space.vars.Kizen\_company\_name</code> admin to update your role.
{% endhint %}

* **A Test or Sandbox Workspace&#x20;**<mark style="color:$success;">**(Recommended)**</mark>**:** This walkthrough uses a fictional business called <code class="expression">space.vars.Theme\_park\_name</code>. Using a test or sandbox workspace prevents changes from affecting your production data.

{% hint style="info" %}
**Note:** Sandbox environments can be set up by your organizations IT team.&#x20;
{% endhint %}

* **Basic Understanding Of Your Own Business Data:**  Understanding your data helps you apply core concepts to real business scenarios. Consider the <code class="expression">space.vars.entities</code> you manage, the interactions you track, and the <code class="expression">space.vars.workflows</code> that drive your operations.
* **Time to Follow the Walkthrough:** Plan for at least 90 minutes to complete the full example.

***

## What's Next?

Now that you have the right permissions, a test workspace, and the required setup, you’re ready to log in for the first time.

Continue to [**Logging In and Navigating the Platform**](/docs/kizen-basics/kizen-in-action/logging-in-and-navigating-the-platform-or-kizen-in-action.md) to learn how to sign in, explore the main navigation, and understand where core features like Data, <code class="expression">space.vars.automation</code>s, Dashboards, and Settings live.


---

# 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/prerequisites-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.