Building a kanban board in Notion and the limits you run into
A team already keeps its notes, specs and meeting records in Notion. Someone suggests putting the work itself there too, because the documentation is already there and nobody wants another login. Ten minutes later a board exists, with columns for To do, Doing and Done, and cards being dragged across it.
That first hour is genuinely good. The question is what happens in month four, when the board has four hundred cards, three people keep asking why a card disappeared from their view, and a client wants read access to one project and nothing else. This article covers how a Notion kanban board is actually put together, the setup decisions that decide whether it survives, the specific places it starts to strain, and what the plans cost at the time of writing.
A board in Notion is a database wearing a different layout
The single most useful thing to understand is that a board is not an object in Notion. It is a database shown with the board layout, grouped by one property. Cards are pages. Columns are the values of the property chosen for grouping, usually a select or status property.
Two consequences follow, and both matter.
Every card is a full document. A card can hold headings, tables, embedded files, and a nested database. For work where the specification and the task should live together, this is a real advantage that dedicated board tools rarely match.
The board is one of several views of the same data. The same database can be shown as a table for review, a calendar by due date, and a board grouped by owner rather than status. Nothing is duplicated. Adding a view takes seconds, and this is where most of the value of building the board in Notion sits.
The flip side is that everything depends on the property design. Change the grouping property and the whole board rearranges. Rename a status value and every card carrying it moves with the rename. Delete a value and the cards fall into an ungrouped bucket. Deciding the properties carefully at the start is not optional polish, it is the difference between a board that lasts and one that gets rebuilt in March.
Setting one up so that it still works in six months
Decide the grouping property before anything else
Use a status or select property with a small number of values. Four to six columns is enough for most teams. Every extra column is a place for cards to sit and be forgotten. If a value is really a category rather than a stage, for example Bug or Feature, make it a separate property and use it for filtering, not for a column.
Add the properties you will want to filter on later
Retrofitting a property onto four hundred cards is tedious, so add them early even if they stay empty at first. A person property for the owner, a date property for the due date, a select for the client or the product area, and a number for a rough estimate cover most needs. A checkbox for blocked is often more useful than a whole column for it.
Build views instead of building boards
Create one database and several views. A board for the daily work, a table filtered to items with no owner, a calendar for anything with a date, and a board grouped by person for a weekly check. Resist the temptation to create a second database for a second project. Use a project property and filter.
Write the column rules down somewhere on the page
Notion gives no mechanism to enforce what it takes for a card to move from one column to the next. A short callout at the top of the page stating the rule, for example that nothing enters Doing without an owner and a date, is the closest thing available. It works only if the team reads it, which is a reason to keep it to three lines.
Plan where finished cards go on the first day
A Done column grows without limit, and a board with two hundred completed cards in the last column is slow to load and unpleasant to read. Two approaches work. Either add an Archived value to the status property and filter the board view to exclude it, or add a checkbox property called Archived and filter on that, which leaves the status intact as a record of how the card finished. Either way, decide before the column is long, because filtering two hundred cards one at a time is nobody's idea of a good afternoon. Keep a separate table view with no filter so the archived work stays searchable, since a finished card is usually the fastest answer to the question of how something was done last time.
Decide who can see what before inviting anyone
Permissions in Notion apply to pages and to the workspace, and a database inherits from the page it lives on. Putting a client board deep inside a page that also contains internal notes is how information leaks. Give each externally shared board its own top level page.
Where a Notion board starts to strain
None of the following makes Notion a poor choice. They are the specific edges that teams tend to hit, and knowing them in advance is worth more than a general verdict.
No work in progress limits. Kanban's main discipline is capping how many items can sit in a column at once. Notion has no setting for this and no warning when a column grows. Teams that rely on WIP limits end up writing the number in the column name and hoping.
Speed on large databases. A board with hundreds of cards, several rollups and a few formula properties becomes noticeably slower to load than a purpose built board, particularly on a phone. Filtering the board view to the current quarter usually fixes this, at the cost of remembering to do it.
Notifications are page centred. Notion notifies on mentions and on updates to pages a person follows. There is no concept of a card moving into a column triggering a message to the person who now owns it. Teams typically bridge this with an automation or by mentioning the new owner in a comment.
File uploads on the free plan. The pricing page states a 5 MB limit per file on the free plan, with unlimited uploads on the paid plans. A board used to review design work or video will hit this quickly.
Page history on the free plan. Version history is listed as 7 days on the free plan, 30 days on Plus and 90 days on Business. If the board is the record of what was decided and when, the shorter window is worth knowing about before it matters.
External guests. The free plan lists a limit of 10 external guests. For an agency running several client boards with two or three people each, that ceiling arrives sooner than expected.
Everything is editable by default. The same flexibility that lets someone add a useful property also lets someone rename a status value at eleven at night and rearrange the board for everyone. Permission controls exist, but on a small workspace most people end up with full edit access.
What the plans cost
Prices below are the list prices shown on the Notion pricing page in United States dollars, checked in September 2026. Notion shows local currency depending on the country, so the figures on screen may differ.
| Plan | Monthly, per seat | Annual, per seat | Page history | File uploads |
|---|---|---|---|---|
| Free | $0 | $0 | 7 days | Up to 5 MB each |
| Plus | $12 | $120 per year, which is $10 a month | 30 days | Unlimited |
| Business | $24 | $240 per year, which is $20 a month | 90 days | Unlimited |
| Enterprise | $35 | Contact sales | Unlimited | Unlimited |
The thing to notice is what the paid tiers are actually buying. For a small team, the jump from Free to Plus is mostly about limits and history rather than about board features. If the board works on the free plan and the only problem is the file size limit, that is a clear and cheap decision. If the board works but the team also needs enforced limits, automatic notifications on movement, or a Gantt view of the same cards, the paid tier does not change those, and the question becomes whether the board belongs in Notion at all.
When a Notion board is the right answer
A Notion board is a good fit when the documentation and the work are genuinely the same thing. Content calendars, research pipelines, hiring processes and product discovery all benefit from a card that is also a document. The team is already in Notion every day, so nothing new has to be learned or paid for.
It is also a good fit when views matter more than process. Being able to look at the same items as a table, a calendar and a board, with a filter per person, solves a lot of coordination without any ceremony.
It fits less well when the board is the operational surface for a team that runs on flow. Software teams with WIP limits, agencies juggling ten client boards and a guest list, and operations teams who need the card to notify its new owner all tend to end up adding a second tool or a set of automations to fill the gaps. At that point the honest comparison is between Notion plus its workarounds and a tool where those behaviours are built in. A side by side comparison with Notion sets out what each side covers.
A useful way to decide is to ask what breaks first. If the answer is a missing feature, look at what other tools include by default on their features page. If the answer is cost per seat as the team grows, compare the per seat prices, since board tools vary widely on that.
Migrating a board out of Notion, if it comes to that
Teams usually delay this decision because the export looks painful. It is worth knowing the shape of it in advance.
A Notion database exports to CSV, with one row per card and one column per property. What does not come across cleanly is the page body of each card, which is where the useful detail often lives, along with comments and file attachments. The pragmatic approach is to export the CSV for the structured fields, keep the Notion pages as reference documentation, and link to them from the new board rather than trying to move every word.
That split is often the better end state anyway. Documentation stays where documentation is good, and the running board moves to a tool built for running boards. Most board tools import from a CSV, and some offer a direct route from other board tools, which is worth checking against what the team actually has. The import page describes how a Trello export is handled, for comparison.
What to change first
Before deciding anything about tools, fix the grouping property and the missing properties on the board that already exists, then add a table view filtered to cards with no owner. Most of the pain blamed on Notion comes from a board that was built in ten minutes and never revisited. If the board is well built and the gaps that remain are WIP limits, notifications on movement, or a Gantt view of the same cards, Pinateca covers those in its free tier for up to five people and ten boards.
Q1. Can a Notion board enforce a work in progress limit?
No. Notion has no setting that caps the number of cards in a column or warns when a column grows past a number. Teams that want the discipline usually write the limit into the column name as a reminder and rely on a regular review to catch breaches.
Q2. Is the free plan enough for a small team's kanban board?
Often yes, for the board itself. The constraints that tend to bite first are the 5 MB per file upload limit, the 7 day page history, and the limit of 10 external guests. If none of those apply to the work, the free plan will carry a small team a long way.
Q3. Should each project get its own database or its own view?
One database with a project property and filtered views is almost always better. Separate databases per project mean a person cannot see all of their work in one place, and every new view has to be rebuilt for every project.
Q4. Why do cards vanish from the board?
Nearly always a filter on the view, or a status value that was renamed or deleted so the cards no longer match any group. Check the view's filter first, then the grouping property's values. Notion keeps the cards, they are simply not being shown.
Q5. Can a client be given access to one board without seeing the rest of the workspace?
Yes, by sharing the specific page the database lives on rather than the workspace. The important part is that the page must not sit inside another page containing internal material, because it is easy to share the parent by accident.
