Kanban board
A custom component that lays out the rows of one of your tables as cards, one lane per value of its status field. Drag a card to another lane (or use Move on a phone), add a card at the bottom of any lane, search by title, and open a card to edit its fields in a side sheet. When the field is the table's lifecycle, the board follows the platform's rules: cards move one stage at a time, and closing values such as cancelled can be reached from any open stage. Lane counts are real totals, an optional work-in-progress limit flags a crowded lane, and each role can only do what its permissions allow.
What it adds to your app
Component KanbanBoard (props: entity, statusField, lanes, titleField, fields, cardFields, limits, detailRoute). A Board page for the role you choose.
Pages
/kanbanBoard (‹page_role›)
Components
KanbanBoardA kanban board over ‹entity›: one lane per ‹status_field› value, drag or Move to change it, quick add per lane, search, and a card sheet to edit fields
Set it up
It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.
- Pick the project
Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).
- Point it at your tables and roles
Leave out the ones with defaults; a wrong one is refused with the options your app has.
Param What it is Example entityThe table whose rows become cards. taskstatus_fieldThe choice field whose values become the lanes, in order. Optional. statuspage_roleThe role the Board page is for. Optional. staff - Preview, then apply to dev
A dry run shows the diff and the check report; applying it changes your dev environment only.
- Deploy
When dev looks right, deploy. Production gets a snapshot first, so you can roll back.
Use it with your coding agent
The agent reads the template, runs a dry run, shows you the diff and applies it.
Add the Kanban board template (slug "kanban") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table on the board; status_field: status field; page_role: who sees the board).{
"tool": "use_template",
"arguments": {
"slug": "kanban",
"project_id": "<your project id>",
"params": {
"entity": "task",
"status_field": "status",
"page_role": "staff"
},
"dry_run": true
}
}appbricx templates use kanban --param entity=task --param status_field=status --param page_role=staff --dry-runGoes well with
Kanbo
Team project board with drag-and-drop cards, checklists, comments and my work.
AI chat panel
A private AI assistant inside your app that answers from the records each person is allowed to see, with saved conversations.
Overdue alerts
Each morning, flags rows past their due date, tells the person assigned and sends the team a list.