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

# App Development

Learn how Kizen plugins extend the platform using JavaScript, including supported integration points and how plugins interact with the Kizen UI and data.

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Provides an overview of the <code class="expression">space.vars.Kizen\_company\_name</code> plugin ecosystem and explains how plugins extend the platform.
{% endhint %}

## Overview

Plugins extend <code class="expression">space.vars.Kizen\_company\_name</code> by adding custom functionality directly into the platform using JavaScript. Plugins run in the end user’s browser inside a web worker and interact with <code class="expression">space.vars.Kizen\_company\_name</code> through defined extension points in the UI and data model.

Because plugins execute client-side, they should be treated as open source. Application code must not include secret keys or sensitive credentials. Secure data access is handled through <code class="expression">space.vars.Kizen\_company\_name</code>'s platform APIs and configuration mechanisms.

### What Plugins Can Do

Plugins in <code class="expression">space.vars.Kizen\_company\_name</code> can be used to:

* Extend the <code class="expression">space.vars.Kizen\_company\_name</code> UI with custom actions and components
* Embed external or custom-built experiences directly into the platform
* Interact with <code class="expression">space.vars.Kizen\_company\_name</code> data through supported APIs
* Enhance workflows without modifying core platform behavior

***

## How Plugins Integrate with Kizen

The <code class="expression">space.vars.Kizen\_company\_name</code> plugin ecosystem connects to the platform through several supported extension points, including:

* [Toolbar items](/docs/integrations-and-plugins/plugin-development/toolbar-items.md) — Add custom actions to <code class="expression">space.vars.Kizen\_company\_name</code> toolbars
* [Persistent floating frames](/docs/integrations-and-plugins/plugin-development/floating-frames.md) — Display always-available plugin interfaces
* [Pages](/docs/integrations-and-plugins/plugin-development/embedded-pages.md) — Render full-page plugin experiences
* [Blocks](/docs/integrations-and-plugins/plugin-development/embedded-blocks.md) — Insert plugin content into existing <code class="expression">space.vars.Kizen\_company\_name</code> pages
* [Data field adornments](/docs/integrations-and-plugins/plugin-development/data-adornments.md) — Enhance or augment specific fields with plugin behavior

Each integration type supports different use cases and levels of interaction with the <code class="expression">space.vars.Kizen\_company\_name</code> UI.

***

## What’s Next

Review the plugin development documentation to learn how to build, configure, and deploy plugins using these integration points. Individual topics cover plugin structure, supported APIs, security considerations, and implementation examples.

<details>

<summary>Related Topics</summary>

* [Toolbar Items](/docs/integrations-and-plugins/plugin-development/toolbar-items.md)
* [Floating Frames](/docs/integrations-and-plugins/plugin-development/floating-frames.md)
* [Pages](/docs/integrations-and-plugins/plugin-development/embedded-pages.md)
* [Blocks](/docs/integrations-and-plugins/plugin-development/embedded-blocks.md)
* [Data Adornments](/docs/integrations-and-plugins/plugin-development/data-adornments.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/integrations-and-plugins/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.