Navigating the Platform & Organizing with Kapps

Before we build anything, let’s get familiar with how the Kinetic Platform is organized and where all the pieces fit together. In this section, you'll learn how to navigate the platform and use Kapps to group related assets like forms, categories, and workflows.

---

What is a Kapp?

A Kapp (short for Kinetic Application) is like a digital folder that holds everything related to a specific business function, workflow, or service area. It contains all the forms, categories, workflows, and configurations tied to that purpose.

Use Kapps to organize different parts of your business without overlap or confusion. Each Kapp is self-contained, making it easy to maintain permissions, build workflows, and report on activity within a specific domain.

---

Kapp Use Case Examples

Here are just a few ways teams across an organization might use Kapps:

💡

Pro Tip: If a business function or team needs its own set of forms and workflows with specific access rules or logic, it’s a good candidate for a Kapp.

---

Kapps vs Spaces

Let’s clarify the two main layers of organization:

• Space: Your overarching environment. Think of it as your workspace — a container for everything, including users, teams, plugins, and Kapps.
• Kapp: A functional area inside a Space that contains related forms, workflows, and configuration.

---

Navigating the Platform

When you log into the Kinetic Experience Platform, you'll land in your Space Console, the main navigation panel on the left-hand side of the screen.

There are four main sections you'll interact with:

Insights

This is where you can view high-level activity and performance across your Space. You’ll find:

• Dashboard (Home): A quick overview of recent activity
• Logs: Detailed logs of integration runs and platform behavior
• Activity: Track runs, errors, workflow triggers, and webhook jobs

Use this section to monitor health, troubleshoot issues, and confirm your automations are running as expected.

Build

The Build section is where you'll do most of your hands-on work. It includes:

• File Resources: Assets like images, templates, and supporting files
• Kapps: Containers for related forms, workflows, and categories
• Models: Data models used to structure custom data entities
• Workflow: Define global workflows that operate across the platform (not tied to a specific form)

This is where you’ll spend time creating forms, logic, and automation.

Configuration

This section is all about managing what powers your platform:

• Plugins: Where you configure integrations (e.g., ServiceNow, internal APIs)
• Settings: Control front-end rendering sources and platform-wide security policies
• Teams: Group users for assignment, notifications, and access control
• Translations: Manage multi-language support for forms and experiences
• Users: Add, manage, or remove access to the platform

Think of Configuration as your platform's command center.

Definitions

Definitions house the foundational pieces your platform relies on:

• Attributes: Custom metadata you can assign to users, teams, or submissions
• Security: Define roles, permissions, and access control policies
• Webhooks: Create outbound triggers to external systems based on platform events

---

🧪

Throughout this guide, we’ll primarily focus on the Build section, but you’ll dip into Configuration and Definitions when you need to manage integrations, teams, or platform-wide settings.

---

Create Your First Kapp: Onboarding

Let’s create a Kapp that will contain everything related to employee onboarding.

Steps:

1. In the Space Console, go to the Build section
2. Select Kapps
3. Click + New Kapp in the top-right
4. Name your Kapp: Onboarding
   • Slug will auto-fill (you can leave it as-is)
5. Click Create

Once your Kapp is created, click into it and explore the Settings under the Configuration section:

• Details
• Attributes
• Security
• Integrations

💡

Expand your knowledge: Dive deeper into Kapp Configuration Options

---

Where You'll Build Next

Now that your Kapp is ready, here’s what you’ll be building inside it:

• Forms to collect user input (like onboarding requests)
• Workflows to automate approvals and actions
• Integrations to connect with other systems like ServiceNow

---

What You Should See

After completing this section, you should now:

• Understand the difference between a Space and a Kapp
• Know where key navigation areas are within the platform
• Have a new Kapp named Onboarding ready to go

---

Expand Your Knowledge

• Overview of the Kinetic Platform Architecture
• Introduction to the Space Console

---

Next up: Build Your First Form — start capturing information inside your newly created Kapp!