> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/key-components/form-studio.md). # Form Studio ### What It Is **Form Studio** is the dedicated tool for building dynamic interactive forms in Flexi Kanban. Forms created in Form Studio can be surfaced directly on the Kanban board — opened by a Handler when a user clicks a card element or button — giving teams a way to capture input, update records, and trigger backend operations without ever leaving the board. Forms in Flexi Kanban are not simple data entry screens. They are fully dynamic interfaces that can respond to user input, apply conditional logic, interact with Salesforce data, and trigger Actions — making them a powerful extension of your board's workflow. *** ### What You Can Build with Form Studio Form Studio gives admins full control over form structure, behavior, and logic: #### Form Layout and Fields * Add fields from any Salesforce source object * Arrange fields into sections and layouts * Configure field labels, defaults, validation, and visibility conditions #### Dynamic Behavior * **Conditions** — show or hide fields, sections, or entire form elements based on user input or record data * **Conditional Styles** — change the appearance of form elements dynamically based on configured rules * **Variables** — define reusable values that can be referenced across the form * **Additional Fields** — virtual fields that exist only within the form context, not mapped to a Salesforce field #### Form Actions and Events Forms in Flexi Kanban support **Handlers** — the same interaction model used on the Kanban board. A Handler on a form element can execute an Action or Action Group, fire an event back to the board, or trigger other configured behavior. This allows forms to interact with the board they are opened from — for example, refreshing a column, updating a card, or moving a record to a new stage after the form is submitted. #### Sharing and Permissions * Configure which users or profiles can access a given form * Form Sharing Rules control visibility independently from board-level permissions *** ### How Forms Connect to the Board Forms are not standalone screens — they are components that get attached to board interactions through Handlers. A typical flow looks like this: 1. An admin builds a form in Form Studio 2. The form is attached to a card element or Custom Button via a Handler in Kanban Studio 3. When a user clicks that element or button on the board, the form opens 4. The user fills in the form and submits 5. The form executes its configured Actions — updating records, triggering automation, or interacting with the board This makes Form Studio one of the key tools for building interactive, workflow-driven Kanban boards that go beyond simple card movement. *** ### When to Use Form Studio Use Form Studio when: * You need users to provide input before or after a board action * You want to guide users through a structured data entry process without leaving the board * You need conditional logic that adapts the form based on what the user selects * You want form submission to trigger backend operations via Actions or Action Groups Learn more in [Building Forms in Form Studio](https://claude.ai/chat/3ff2e1a4-8052-48a2-8c2f-8ff0fe64eda1#). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.flexikanban.ai/key-components/form-studio.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.