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.

View the files
Kanban board: the Board page, added to Relay, on desktopKanban board: the Board page, added to Relay, on a phone

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

  • /kanban Board (‹page_role›)

Components

  • KanbanBoard A 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.

  1. Pick the project

    Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

  2. Point it at your tables and roles

    Leave out the ones with defaults; a wrong one is refused with the options your app has.

    ParamWhat it isExample
    entityThe table whose rows become cards.task
    status_fieldThe choice field whose values become the lanes, in order. Optional.status
    page_roleThe role the Board page is for. Optional.staff
  3. Preview, then apply to dev

    A dry run shows the diff and the check report; applying it changes your dev environment only.

  4. 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.

Prompt
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).
MCP call
{
  "tool": "use_template",
  "arguments": {
    "slug": "kanban",
    "project_id": "<your project id>",
    "params": {
      "entity": "task",
      "status_field": "status",
      "page_role": "staff"
    },
    "dry_run": true
  }
}
CLI
appbricx templates use kanban --param entity=task --param status_field=status --param page_role=staff --dry-run

Your agent adds it. Appbricx runs it.

Start freeAll templates