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

This page introduces how to create your first Business in <code class="expression">space.vars.Kizen\_company\_name</code>. Business workspaces allow you to store data and provides the foundation for everything you build. Creating a Business also generates a unique Business ID used for API requests and integrations. Reviewing this walkthrough will help you set up your workspace so you can begin organizing data, building <code class="expression">space.vars.workflows</code>, and managing operations within your Business.

### **Why This Matters**

A well-structured Business workspace ensures:

* Clean and organized data
* Accurate <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code>
* Correct role and permission behavior
* Reliable <code class="expression">space.vars.dashboards</code> and analytics
* A setup that scales as your organization grows

Starting with a strong Business workspace configuration reduces confusion and prevents rework later.

***

## **Before You Begin**

Most users **cannot** create a Business. You must be an Administrator with the correct permissions.

* If you’re not an Admin, ask one in your organization to create a sandbox or training workspace for you.
* If your Admin does not have permission to create a Business, contact <code class="expression">space.vars.Kizen\_company\_name</code> Support to have one made.

***

{% stepper %}
{% step %}

#### Select the **Profile** icon

{% endstep %}

{% step %}

#### In the dropdown menu, select **Add Business**

{% endstep %}

{% step %}

#### Enter your **Company Name** & **Business Name**

For this tutorial:

* Company Name: <code class="expression">space.vars.Theme\_park\_name</code>&#x20;
* <code class="expression">space.vars.Kizen\_company\_name</code> Business Name: Flywheel - Austin Location

{% hint style="info" %}
**Note:** The Company Name field should contain your company’s legal or public name. The <code class="expression">space.vars.Kizen\_company\_name</code> Business Name is the name of your workspace within <code class="expression">space.vars.Kizen\_company\_name</code>.
{% endhint %}

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

{% step %}

#### Select **CREATE FROM SCRATCH**

<mark style="color:$success;">**(Optional)**</mark> You can also choose **CREATE WITH AI** to have <code class="expression">space.vars.Kizen\_company\_name</code> generate a starter Business.&#x20;
{% endstep %}
{% endstepper %}

The workspace you have just created will now become your base for building, testing, and analyzing every part of your <code class="expression">space.vars.Theme\_park\_name</code> use case. A unique Business ID was also created which will be needed for sending API authorizations.

{% hint style="info" %}
**Note:** If you have or are creating multiple business workspaces and are building APIs in each space, you will need to the unique `X-BUSINESS-ID` string for the space you want to modify.
{% endhint %}

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

***

## How This Fits Into Agentic Workflows

Creating a Business is the foundation for all <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> in <code class="expression">space.vars.Kizen\_company\_name</code>. Every <code class="expression">space.vars.workflow</code>, <code class="expression">space.vars.automation</code>, integration, and API interaction runs within the context of a Business.

Once a Business is created, it becomes the container where:

* <code class="expression">space.vars.objects</code> are defined and connected
* <code class="expression">space.vars.activities</code> are scheduled and logged
* <code class="expression">space.vars.automations</code> are triggered and executed
* Users, roles, and permissions are enforced
* External systems integrate through APIs and connectors

<code class="expression">space.vars.workflows</code> rely on the Business to understand *which data*, *which users*, and *which rules* apply. Without a Business, <code class="expression">space.vars.automations</code> have no context for where <code class="expression">space.vars.entities</code> live or how processes should behave.

For example, when you automate a follow-up <code class="expression">space.vars.activity</code>, trigger an email, or sync data from an external system, <code class="expression">space.vars.Kizen\_company\_name</code> uses the Business to determine:

* Which <code class="expression">space.vars.entities</code> to act on
* Which <code class="expression">space.vars.workflows</code> are allowed to run
* Which permissions apply to each action

By creating your Business first, you enable <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> to operate consistently, securely, and at scale as your platform usage grows.

***

## Business Workspace Capabilities By Role

{% columns %}
{% column %}

#### Admins

* Create and manage Business workspaces
* Configure Business-level settings, including name, industry, and preferences
* Manage users, roles, and permissions within a Business
* Define which <code class="expression">space.vars.objects</code>, <code class="expression">space.vars.activities</code>, and features are available to teams
* Ensure data isolation and security between Business workspaces
  {% endcolumn %}

{% column %}

#### Technical Builders

* Build <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> scoped to a specific Business
* Use the unique Business ID to create API calls for creating, updating, and searching <code class="expression">space.vars.entities</code>
* Integrate external systems and services at the Business level
* Configure connectors, webhooks, and event-driven <code class="expression">space.vars.workflows</code>
* Use Business-level context to support reporting, data sync, and orchestration
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

While this guide uses a general setup example, a Business workspace in <code class="expression">space.vars.Kizen\_company\_name</code> maps directly to how organizations structure data, <code class="expression">space.vars.workflows</code>, and compliance boundaries across industries. Each Business acts as a secure, isolated environment where operations, users, and <code class="expression">space.vars.automations</code> are managed together.

{% tabs %}
{% tab title="Insurance" %}
In insurance, a Business workspace often represents a carrier, agency, or line of business.

Common examples include:

* Separating personal, commercial, and specialty insurance operations
* Managing multiple agencies or regions within distinct Business workspaces
* Isolating data and <code class="expression">space.vars.workflows</code> for compliance and regulatory requirements

By using Business workspaces, insurance teams ensure policies, claims, and client data remain properly scoped and compliant.
{% endtab %}

{% tab title="Healthcare" %}
In healthcare, a Business workspace can represent a practice, department, or care organization.

Common examples include:

* Managing separate clinics or service lines
* Isolating patient data by department or location
* Enforcing role-based access for clinical and administrative staff

Business workspaces help healthcare organizations maintain privacy, structure care <code class="expression">space.vars.workflows</code>, and support regulatory requirements such as HIPAA.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, a Business workspace often maps to a firm, division, or client segment.

Common examples include:

* Separating retail, wealth management, and institutional operations
* Managing multiple advisory teams or branches
* Enforcing compliance controls across accounts and <code class="expression">space.vars.workflows</code>

By structuring operations into Business workspaces, financial teams maintain data integrity, improve governance, and scale securely.
{% endtab %}
{% endtabs %}

***

## **What’s Next?**

Continue to [Understanding your Business Settings](/docs/kizen-basics/kizen-in-action/configure-your-business-settings-or-kizen-basics.md) to start modeling <code class="expression">space.vars.Theme\_park\_name</code>'s core data. You'll use this information to set roles, permissions, and edit your business information & customizations.


---

# 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-business-workspace-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.