# Configure Your Business Settings | Kizen Basics

## Overview

Before your team begins working in <code class="expression">space.vars.Kizen\_company\_name</code>, an administrator needs to establish the foundations of your workspace. This topic walks you through three core setup tasks in the **Settings** area:

1. Editing your business information
2. Adding team members
3. Creating roles

Together, these tasks ensure that your workspace reflects your organization's identity, and that the right people have access.&#x20;

Throughout this topic, <code class="expression">space.vars.Theme\_park\_name</code> is used as the example business. You will add Jacob Mulligan and Sally Woods as team members as a Guest Services and Concession Stand Cook Staff.

{% hint style="info" %}
**Note**: In this tutorial, permissions on roles and team members will not be covered. To learn more about permission basics, review [Configure Your First Permissions](/docs/kizen-basics/kizen-in-action/configure-your-first-permission-groups-or-kizen-basics.md).
{% endhint %}

### Why This Matters&#x20;

Setting up your business information, team members, and roles correctly is not administrative overhead. It directly determines how effectively your organization operates inside the platform.

Without a clear structure:

* Users may have too much or too little access, leading to security risks or blocked <code class="expression">space.vars.workflows</code>
* Teams waste time navigating irrelevant data
* Reporting, ownership, and accountability become inconsistent

With a well-defined setup:

* Each team member sees only what they need, reducing errors and confusion
* Sensitive data is protected through controlled access
* <code class="expression">space.vars.workflows</code> run more smoothly because responsibilities and visibility are aligned
* Scaling your team becomes significantly easier since roles are already structured

This foundation ensures your workspace is not just functional, but controlled, secure, and aligned with how your business actually operates.

***

## Before You Begin

Before starting, confirm the following:

* You are logged in to <code class="expression">space.vars.Kizen\_company\_name</code> with an **Administrator** account. Only Admins can access and modify business settings.
* You have the full names and business email addresses of the team members you plan to add.
* Your business logo is available as an image file if you plan to upload it during the business information step.

***

## Configuring Your Business

### Task 1: Edit Your Business Information

Your business information appears throughout <code class="expression">space.vars.Kizen\_company\_name</code> and helps identify your workspace. Keep this information accurate so your team and any client-facing outputs reflect your brand correctly.

{% stepper %}
{% step %}

#### **Navigate to Settings using the main navigation menu.**

You'll land on **Business Information** (or Business Settings) from the **Settings** menu.

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

{% step %}

#### In the **Business Name** field, enter or confirm your organization's name.&#x20;

For this example, make sure it's: <code class="expression">space.vars.Theme\_park\_name</code>

Update any additional fields as needed, such as your business address, phone number, time zone, and date format preferences.

Upload your business logo if desired by selecting the logo upload area and choosing your image file.

Select **SAVE** to apply your changes.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note:** Timezone and date format settings affect how dates and times display across the platform for all users in your workspace. Set these carefully before your team begins logging <code class="expression">space.vars.activity</code>.
{% endhint %}

### Task 2: Add Team Members

Adding team members gives individuals access to your <code class="expression">space.vars.Kizen\_company\_name</code> workspace. Each team member is invited via email and must accept the invitation to complete account setup.

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

{% stepper %}
{% step %}

#### **In Settings, select Team, Roles, & Permissions.**

Select **NEW TEAM MEMBER**.
{% endstep %}

{% step %}

#### Enter the first team member's details:

* **First Name:** Jacob
* **Last Name:** Mulligan
* **Email:** <jacobmilligan@flywheel.com> (this is a fake email address)
* **Phone Number:** *Blank*
* **Set Roles(s)**: You'll assign Jacob a role once we have created one.
* **Add Additional Permission Group(s):** *Flywheel Guest Staff*
* Leave the remaining fields as default

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

{% step %}

#### Select SAVE

{% endstep %}
{% endstepper %}

Jacob Mulligan will appear in your Team Members list with a **Unverified** status until they accept their invitations and complete setup.

### Task 3: Create Roles

Roles describe the job functions or positions within your organization. They help you organize your team and can be used throughout <code class="expression">space.vars.Kizen\_company\_name</code> to assign ownership and filter <code class="expression">space.vars.entities</code>.

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

{% stepper %}
{% step %}

#### **In Settings, select Roles.**

Select **NEW ROLE**
{% endstep %}

{% step %}

#### **Enter the name** of the first role: Guest Services Staff

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

Set **Default Permission Group(s**): *Flywheel Guest Staff*

**Default for New Users**: Leave toggled off

Select **SAVE** to create the role.
{% endstep %}
{% endstepper %}

The role of Guest Services Staff now appears in your **Roles** list and is available to assign to team members. You can now go back to **Teams** tab, edit Jacob Mulligan, and assign him to be a **Guest Services Staff** role.

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

***

## Apply What You've Learned

Now that you've created the Guest Staff Services role for Jacob Mulligan, add another team member and assign them the correct role.

**Team Member Details**

* **First Name:** Sally
* **Last Name:** Woods
* **Email:** <sallywoods@flywheel.com> *(this is a fake email address)*
* **Phone Number:** *Blank*
* **Role Name:** Concession Stand Cook
* **Permissions Group**: *Flywheel Concession Staff*

After completing this step, you should have:

* **Jacob Mulligan** and **Sally Woods** in the **Team** tab.
* **Guest Services Staff** and **Concession Stand Cook** in the **Roles** tab.

***

## How This Fits Into Agentic Workflows

Business Settings define the environment that <code class="expression">space.vars.workflows</code>, <code class="expression">space.vars.automations</code>, and users operate within.

Once configured, they influence three critical areas: **timing, communication, and user context**.

* **Timing:** <code class="expression">space.vars.automations</code> run based on your Business time zone. Scheduled <code class="expression">space.vars.workflows</code>, reminders, and <code class="expression">space.vars.activity</code> logging all follow this setting.
* **Communication:** Emails and messages triggered by <code class="expression">space.vars.workflows</code> use your Business-level defaults, such as sender address and phone configuration.
* **User context (roles and team members):** <code class="expression">space.vars.workflows</code> operate on <code class="expression">space.vars.entities</code> that are owned, updated, or assigned to specific team members.

For example:

* A <code class="expression">space.vars.workflow</code> that assigns a follow-up task will assign it to a **team member** with the appropriate role
* Notifications and <code class="expression">space.vars.activities</code> are tied to specific **users**, not just <code class="expression">space.vars.entities</code>

By configuring Business Settings alongside your team and roles, you ensure <code class="expression">space.vars.workflows</code> run correctly and reach the right people.

***

## Business Workspace Capabilities By Role

{% columns %}
{% column %}

#### Admins

* Configure Business Settings (name, branding, time zone, communication defaults)
* Add and manage team members
* Create and manage roles
* Ensure <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> operate within the correct access boundaries
  {% endcolumn %}

{% column %}

#### Technical Builders

* Build <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> that assign tasks and update <code class="expression">space.vars.entities</code> based on team structure
* Use roles and user assignments to control how <code class="expression">space.vars.automations</code> route work
* Configure integrations that rely on Business-level context and user access
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back to Your Industry

While <code class="expression">space.vars.Theme\_park\_name</code> demonstrates a physical, guest-facing business, the same setup principles apply to industries where data access, compliance, and role clarity are critical.

{% tabs %}
{% tab title="Insurance" %}
In insurance organizations, teams are often divided between agents, claims processors, and underwriting staff.

* **Agents** need access to client contact <code class="expression">space.vars.entities</code>, policy details, and communication history, but should not have full visibility into underwriting decisions or internal financial data.
* **Claims processors** require access to claims <code class="expression">space.vars.entities</code> and supporting documentation, along with the ability to update claim status and timelines.
* **Underwriters** may need broader access to risk data and policy structures but limited interaction with day-to-day client communication <code class="expression">space.vars.entities</code>.

By defining clear roles, you ensure that sensitive financial and personal data is only accessible to those who need it, reducing compliance risk and operational errors.
{% endtab %}

{% tab title="Healthcare" %}
Healthcare organizations rely heavily on strict access controls due to patient privacy requirements.

* **Front desk staff** need access to patient intake forms, appointment records, and basic contact information.
* **Clinical staff** require access to medical records, treatment history, and care plans.
* **Billing teams** need access to insurance information and payment records but should not modify clinical data.

Using roles allows you to create distinct clinical, administrative, and financial positions. This helps maintain compliance with regulations while ensuring each team can do their job efficiently.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, teams often work across client management, compliance, and operations.

* **Advisors** need access to client profiles, portfolios, and communication history.
* **Operations teams** handle transactions, account updates, and internal <code class="expression">space.vars.workflows</code>.
* **Compliance teams** require visibility into activity logs and records but typically do not modify client data directly.

A structured approach to roles ensures that sensitive financial data is protected while still allowing teams to collaborate effectively. It also makes auditing and oversight significantly easier.
{% endtab %}
{% endtabs %}

***

## What's Next

Now that your workspace is configured with business information, team members, and roles, you are ready to build out the operational tools your team will use daily. Next, [Create Your First Contact Record](/docs/kizen-basics/kizen-in-action/create-your-first-contact-record-or-kizen-basics.md).


---

# 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/configure-your-business-settings-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.