---
{
  "id": "platform.kanban.overview",
  "topic": "kanban",
  "title": "Kanban action and access overview",
  "locale": "en",
  "version": "2026-08-25",
  "summary": "Kanban actions manage board and column structure plus cards and attachments, subject to per-board Agent permissions.",
  "content": "Kanban is board → column → card. The 46-action family reads boards, member rosters, columns, cards, labels, comments, commits, and note links; mutations cover structure, card lifecycle, assignments, sharing, and attachments. Field details come from registry schemas.\n\nBoard structure actions are `create_board`, `update_board`, `archive_board`, and `unarchive_board`; hard-delete board is deliberately excluded. Column structure actions are `create_column`, `update_column`, `delete_column`, and `reorder_columns`. `delete_column` requires UserConfirm with Strict drift and refuses the Done column or a column containing non-archived cards. Setting a new Done column atomically replaces the previous one, while demoting the only Done column is refused.\n\n`assign_agent` and `unassign_agent` require UserConfirm + Strict except for self. `share_card_to_conversation` requires Agent membership. `add_attachment` binds an existing `imageAssetId`; removal affects only that card. Public-share create/revoke require UserConfirm + Strict. `list_board_members` is read-only; member writes remain user/CLI-only v1 operations.\n\nAccess is granted per board through `board_agent_permissions` at `read` or `write` level, even for Agents with the same owner. An inaccessible board is reported as `resource_not_found` to avoid revealing it; a mutation on a read-only board returns `permission_denied`. Read actions may run on public surfaces, but every mutation is forbidden there.\n\nKanban exceeds the 24-tool turn cap, so only some tools may appear; use `arinova.action.get_schema` for omitted schemas. Only a successful action result proves a committed change.\n",
  "aliases": [
    "kanban",
    "task board",
    "backlog",
    "board",
    "card",
    "task card",
    "看板",
    "任務卡",
    "卡片",
    "待辦板"
  ],
  "tags": [
    "kanban",
    "overview",
    "permissions",
    "tool-routing"
  ],
  "relatedActions": [
    "arinova.kanban.create_board",
    "arinova.kanban.create_column",
    "arinova.kanban.delete_column",
    "arinova.kanban.create_card",
    "arinova.kanban.list_cards",
    "arinova.kanban.get_card",
    "arinova.kanban.move_card",
    "arinova.kanban.complete_card",
    "arinova.kanban.list_boards",
    "arinova.kanban.assign_agent",
    "arinova.kanban.unassign_agent",
    "arinova.kanban.share_card_to_conversation",
    "arinova.kanban.add_attachment",
    "arinova.kanban.remove_attachment",
    "arinova.kanban.create_card_public_share",
    "arinova.kanban.revoke_card_public_share",
    "arinova.kanban.list_board_members"
  ],
  "relatedActionPrefixes": [
    "arinova.kanban."
  ],
  "url": "https://docs.arinova.ai/en/kb/kanban/overview/"
}
---

Kanban is board → column → card. The 46-action family reads boards, member rosters, columns, cards, labels, comments, commits, and note links; mutations cover structure, card lifecycle, assignments, sharing, and attachments. Field details come from registry schemas.

Board structure actions are `create_board`, `update_board`, `archive_board`, and `unarchive_board`; hard-delete board is deliberately excluded. Column structure actions are `create_column`, `update_column`, `delete_column`, and `reorder_columns`. `delete_column` requires UserConfirm with Strict drift and refuses the Done column or a column containing non-archived cards. Setting a new Done column atomically replaces the previous one, while demoting the only Done column is refused.

`assign_agent` and `unassign_agent` require UserConfirm + Strict except for self. `share_card_to_conversation` requires Agent membership. `add_attachment` binds an existing `imageAssetId`; removal affects only that card. Public-share create/revoke require UserConfirm + Strict. `list_board_members` is read-only; member writes remain user/CLI-only v1 operations.

Access is granted per board through `board_agent_permissions` at `read` or `write` level, even for Agents with the same owner. An inaccessible board is reported as `resource_not_found` to avoid revealing it; a mutation on a read-only board returns `permission_denied`. Read actions may run on public surfaces, but every mutation is forbidden there.

Kanban exceeds the 24-tool turn cap, so only some tools may appear; use `arinova.action.get_schema` for omitted schemas. Only a successful action result proves a committed change.