Does Slack have a kanban board?

Short answer: partly. Slack Lists includes a board layout that groups items into columns you can drag work between, so Slack does have kanban-style columns natively. What Slack does not have is the machinery around those columns - no work-in-progress limits, no bottleneck or throughput reporting, and no view across more than one list. That distinction decides whether native Slack is enough for your team, or whether you should connect a real board to it.

What Slack gives you natively

Slack ships two surfaces that teams reach for when work needs tracking, and they do different jobs. Knowing which one you are actually using explains most of the confusion behind the question.

Slack Lists: the closest native thing to a kanban board

A Slack list keeps requests out of the scroll, which is the first operational win any team notices: a message that would have vanished up the channel becomes a row someone owns. Every list item carries completion, a name, an assignee and a due date by default, and you can add fields of your own for priority or status. Items support subtasks and their own comment threads.

Switch the layout from table to board and group by a field, and the list renders as columns you can drag items between. Group by a status field and you have a kanban board in the visual sense, saved as a view anyone with list access can open. For triage inside a single channel, that is genuinely enough.

Lists are not purely passive, either. Slack's own list automations can collect requests through a form, post a message when a chosen field changes, and send due-date reminders - either to the person holding the item or as a summary into a channel. For a small team working out of one channel, that covers a surprising amount of ground.

Worth knowing before you standardise on it: a list holds up to 1,000 items and subtasks on Pro and Business+, or 5,000 on Enterprise Grid, and the oldest items archive automatically once you reach the ceiling.

Slack canvases: a document, not a board

Canvases get mistaken for boards because they also have columns. They are not the same thing. A canvas is a document attached to a channel or conversation - notes, checklists, images, links - and its columns (up to three) arrange the page rather than represent workflow stages. Nothing moves through them, so there is no state to report on.

The useful move is to combine the two: embed a Slack list inside a canvas, so a project brief and the work it describes sit on one page. The kanban part is the list, not the canvas.

Where native tracking runs out

Native tracking records what exists, and its automations react to one item at a time - this field changed, this date is near. Delivery work also needs to answer how the whole thing is flowing, and that is where teams hit the wall: usually around the point where one list becomes several, or someone asks why a release slipped and there is no record to consult. Slack Lists does not cap work in progress per stage, rank which stage is slowing delivery, chart created against completed, flag items that have gone quiet, or report across several projects at once.

Native vs integrated, feature by feature

Slack capabilities above reflect Slack's published documentation as of September 2026.

What changes when the board is connected to Slack

The integrated option is not "leave Slack". It is a board that lives in your workflow with Slack wired to it in both directions, so the conversation and the status of the work stop drifting apart.

• Requests stop scrolling away. Run /otper create-card <title> | <description> in a linked channel, or open any message's More actions menu and choose Otper Actions - the first line becomes the title, the rest the description, and attached files come across with it. Either way the card lands in the board's first list, so every Slack request arrives in one predictable intake stage instead of in five people's memories.
• Progress reaches the people who need it, and only them. Every linked channel keeps its own event subscription across four groups - Cards, Board, Lists and Members - so a delivery channel can receive card movement while a leadership channel receives board and member changes only. A channel nobody mutes is a channel that still works when something goes wrong.
• Attribution survives the handoff. Each person links their Slack identity once with /otper login. After that a message-turned-card is attributed to its creator, respects their permissions on that board, and lands in the board's activity history - so "who raised this, and when?" still has an answer months later. Assign an owner on the card itself; creation records who asked, not who is accountable.

Setup is a board-level action, not an admin ticket: open a board you administer, go to Integrations, connect the workspace, and link a channel. One board can post to several channels, and one workspace can serve many boards. The Slack setup guide walks through linking a channel and picking its events, and the full integration write-up covers turning a Slack message into a tracked card in detail.

Which should you pick?

If you are weighing the integrated route in more depth, the companion guide to running a Slack kanban board covers the two-way setup end to end.

FAQ

Related reading

• Slack kanban board: how to run kanban inside Slack
• The Otper Slack integration
• Slack setup guide: connecting a board to a channel
• What the Otper Slack integration does, in full
• Kanban board software in Otper