Last updated
Was this helpful?
⌘Ctrlk
Audience: Admins, Developers, Solution Architects
Purpose: Provides an overview of the Kizen plugin ecosystem and explains how plugins extend the platform.
Plugins extend Kizen 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 Kizen 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 Kizen's platform APIs and configuration mechanisms.
Plugins in Kizen can be used to:
Extend the Kizen UI with custom actions and components
Embed external or custom-built experiences directly into the platform
Interact with Kizen data through supported APIs
Enhance workflows without modifying core platform behavior
The Kizen plugin ecosystem connects to the platform through several supported extension points, including:
Toolbar items — Add custom actions to Kizen toolbars
Persistent floating frames — Display always-available plugin interfaces
Embedded pages — Render full-page plugin experiences
Embedded blocks — Insert plugin content into existing Kizen pages
Data field adornments — Enhance or augment specific fields with plugin behavior
Each integration type supports different use cases and levels of interaction with the Kizen UI.
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.
Last updated
Was this helpful?
Was this helpful?