> 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/apps-and-integrations/plugin-development.md).

# Apps

Extend Kizen's capabilities with apps by adding custom actions, components, and UI elements to the platform. Install them from the App Marketplace, or build your own.

{% hint style="success" %}
**Audience:** Administrators, developers, solution architects

**Purpose:** Describes what Kizen apps are and explains the difference between marketplace apps and business apps
{% endhint %}

## Overview

Kizen *apps* extend the platform with custom functionality. They run in the user's browser inside a Web Worker and interact with Kizen through defined extension points in the UI and data model. Because they execute on the client side, they use server-side managed secrets to secure sensitive data.

{% hint style="info" %}
**Note:** Apps can also use code steps, which run on the server side, unlike the rest of the app's code. For more information, see [Agentic Workflow Code Steps](https://developer.kizen.com/docs/concepts/agentic-workflows/automation-code-steps.md).
{% endhint %}

Apps can:

* Extend Kizen with new actions, components, and UI elements
* Add external or custom-built content
* Interact with <code class="expression">space.vars.Kizen\_company\_name</code> data through supported APIs
* Enhance workflows without modifying core platform behavior

This page covers the following topics:

* [About access and configuration](#about-access-and-configuration)
* [About marketplace apps and business apps](#about-marketplace-apps-and-business-apps)
* [About app development](#about-app-development)

***

## About access and configuration

When you enable a Kizen app, every team member in your business has access to it. Some business-wide features might require configuration beforehand, such as connections to external APIs or app preferences that pertain to every user equally. Apps can also be user-configurable, with preferences that each team member can set for themselves.

{% hint style="info" %}
**Note:** You can disable an app after you install it. Disabling the app doesn't erase its configuration. If you re-enable it, you can begin using it again immediately.
{% endhint %}

***

## About marketplace apps and business apps

The platform supports two kinds of apps: marketplace apps and business apps. Marketplace apps are available for all users of Kizen in any business, whereas business apps are available to their specific business only. See the following table for details:

| Detail                            | Marketplace app                            | Business app                                                 |
| --------------------------------- | ------------------------------------------ | ------------------------------------------------------------ |
| Who is it available for           | All team members of any Kizen business     | A specific business's team members                           |
| How you release it                | Kizen reviews it and lists it              | The business publishes it without Kizen review               |
| Where you discover it or build it | The Marketplace tab of the App Marketplace | The Develop tab of the App Marketplace                       |
| Where you manage it               | The Installed tab of the App Marketplace   | The Installed tab and the Develop tab of the App Marketplace |

For more information, see [Work with Marketplace Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/work-with-marketplace-apps.md) and [Work with Business Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/work-with-business-apps.md).

***

## About app development

In development terms, an app in Kizen is a package of *surfaces*, which are user interfaces with associated behaviors. A manifest file at the root of the app's directory identifies the app and holds its settings. Each surface in the app has its own subdirectory with a declarative JSON configuration file, plus any JavaScript and CSS files for the surface's functionality and styling.

Any Kizen user with the necessary permissions can build an app in Kizen, either manually with the Node-based Kizen CLI or with the assistance of a coding agent like Kizen's own KiCode.

For more information, see [Develop Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/develop-apps.md).

***

## What's next

Continue to [Work with Marketplace Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/work-with-marketplace-apps.md) to learn how to install and configure apps from the App Marketplace.

<details>

<summary>Related Topics</summary>

* [Work with Marketplace Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/work-with-marketplace-apps.md)
* [Work with Business Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/work-with-business-apps.md)
* [Develop Apps](https://developer.kizen.com/docs/apps-and-integrations/plugin-development/develop-apps.md)

</details>

***


---

# 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/apps-and-integrations/plugin-development.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.
