> 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/standard-kanban/howtos-and-best-practices/how-to-display-different-layouts-for-the-same-kanban-card.md).
# How to display different layouts for the same kanban card
Kanban can display different layout tabs for the same card depending on what cell has been clicked by user.
* Create kanban variable that will toggle layout types:
* In Card Layout settings set 'Layout Body' to Standard (Body Configuration tab):
* Go to "Tabs Configuration" and create 2 Layout tabs.
* Set conditions to display each tab using variable you created:
* On the Card Compact layout choose cell that will handle mouse click ("onClick" event) to display specified layout tab:
* Add handlers for "Account Name" cell:
1. "Update Variables" handler sets "2" value to "layoutType" variable, which means that click on Account Name will load layout's "Tab 2" tab (based on layout tabs conditions)
2. "Refresh Card Layout" handler:
* Save Kanban.
Based on the setup above card layout types will switch from 'Tab 1' to 'Tab 2' tab each displaying separate KanBan Form based on what cell user clicks.
---
# 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://docs.flexikanban.ai/standard-kanban/howtos-and-best-practices/how-to-display-different-layouts-for-the-same-kanban-card.md?ask=&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.