> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/kizen-basics/kizen-in-action/prerequisites-or-kizen-in-action.md).

# Prerequisites | Kizen Basics

Review the prerequisites required to complete the Kizen in Action walkthroughs, including account access and permissions.

## Overview

Before starting the <code class="expression">space.vars.Kizen\_company\_name</code> Basics in Action walkthroughs, confirm you have the right access, permissions, and environment setup. Each walkthrough assumes these are already in place, so gaps here are the most common reasons users get stuck partway through the examples.

### 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 to [log in](https://go.kizen.com/) to  <code class="expression">space.vars.Kizen\_company\_name</code>  so you can follow along and complete each step in the example.
* **Admin Permissions:** Ensure you are an 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

To check your role, go to **Settings** > **Team, Roles, & Permissions** and find your name in the list. Your Role(s) column should show **Admin**.

{% 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 Separate Business Workspace&#x20;**<mark style="color:$success;">**(Recommended)**</mark>**:** This walkthrough uses a fictional business called <code class="expression">space.vars.Theme\_park\_name</code>. Creating a separate Business Workspace for this walkthrough, rather than using your organization's real one, keeps these practice steps from affecting your production data.

{% hint style="info" %}
**Note:** Sandbox environments can be set up by your organization's IT team. <code class="expression">space.vars.Kizen\_company\_name</code> doesn't offer a distinct sandbox environment. To check which workspace you're currently in, look at the workspace name in **Settings** > **Business Information**.
{% 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.kizen.com/docs/kizen-basics/kizen-in-action/prerequisites-or-kizen-in-action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.