Create Your First Business Workspace | Kizen Basics
Overview
Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
This page introduces how to create your first Business in Kizen. 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 Workflows, and managing operations within your Business.
Why This Matters
A well-structured Business workspace ensures:
Clean and organized data
Accurate Workflows and Agentic Workflows
Correct role and permission behavior
Reliable Dashboards 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 Kizen Support to have one made.
The workspace you have just created will now become your base for building, testing, and analyzing every part of your Flywheel Adventure Park use case. A unique Business ID was also created which will be needed for sending API authorizations.
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.
How This Fits Into Agentic Workflows
Creating a Business is the foundation for all Workflows and Agentic Workflows in Kizen. Every Workflow, Agentic Workflow, integration, and API interaction runs within the context of a Business.
Once a Business is created, it becomes the container where:
Objects are defined and connected
Activities are scheduled and logged
Agentic Workflows are triggered and executed
Users, roles, and permissions are enforced
External systems integrate through APIs and connectors
Workflows rely on the Business to understand which data, which users, and which rules apply. Without a Business, Agentic Workflows have no context for where Records live or how processes should behave.
For example, when you automate a follow-up Activity, trigger an email, or sync data from an external system, Kizen uses the Business to determine:
Which Records to act on
Which Workflows are allowed to run
Which permissions apply to each action
By creating your Business first, you enable Workflows and Agentic Workflows to operate consistently, securely, and at scale as your platform usage grows.
Business Workspace Capabilities By Role
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 Objects, Activities, and features are available to teams
Ensure data isolation and security between Business workspaces
Technical Builders
Build Workflows and Agentic Workflows scoped to a specific Business
Use the unique Business ID to create API calls for creating, updating, and searching Records
Integrate external systems and services at the Business level
Configure connectors, webhooks, and event-driven Workflows
Use Business-level context to support reporting, data sync, and orchestration
Tying It Back Into Your Industry
While this guide uses a general setup example, a Business workspace in Kizen maps directly to how organizations structure data, Workflows, and compliance boundaries across industries. Each Business acts as a secure, isolated environment where operations, users, and Agentic Workflows are managed together.
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 Workflows for compliance and regulatory requirements
By using Business workspaces, insurance teams ensure policies, claims, and client data remain properly scoped and compliant.
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 Workflows, and support regulatory requirements such as HIPAA.
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 Workflows
By structuring operations into Business workspaces, financial teams maintain data integrity, improve governance, and scale securely.
What’s Next?
Continue to Understanding your Business Settings to start modeling Flywheel Adventure Park's core data. You'll use this information to set roles, permissions, and edit your business information & customizations.
Last updated
Was this helpful?