How to Share a Kanban Board With Clients, Free
“Can you send me an update?” is the most expensive sentence in client work. Every time you answer it by hand, you copy statuses into an email that's stale before it arrives. The fix is to share your kanban board with clientsdirectly — but the moment you try, most tools ask you to buy another seat, and your client has to create an account they never wanted. Here's how to do it without either.
Why sharing a board with clients usually gets expensive
Project tools price by user. On Trello, bringing a client into a workspace counts against the free plan's 10-collaborator limit, and single-board guest access is a Standard-plan feature at $5 per user per month. Asana and Monday.com work the same way — Monday's free plan covers just 2 seats. So a five-client agency that wants each client to see one board ends up paying for five people who log in once a month.
Then there's the friction on their side. A client asked to create an account, confirm an email and learn a new UI just to check whether you shipped the homepage will simply email you again instead. Adoption dies at the signup screen.
The read-only link approach
The alternative is a public read-only link: one URL that renders the board — lists, cards, labels, dates, checklist progress — to anyone who opens it, with no account and no seat. Your client clicks and sees the current state of the work. They can't drag anything, rename anything or leave a comment, which is usually exactly what you want.
In Decknote this lives in the Share modal: flip Public link on and you get a URL you can copy into any email or chat. Opening it shows the board read-only, and clicking a card opens its description as a page — so a client can read the spec you already wrote instead of asking you to summarize it. The page carries a noindextag, so it won't show up in search results.
What to share and what to keep private
A public board is public to whoever has the link, so the work is in deciding which board that is. Two patterns work well:
- A board per client. Their board holds only their work and is the one you share. Your internal board — with rates, other clients, half-formed ideas — stays private. This is the cleanest option and the one most agencies land on.
- A public-facing mirror. Keep messy execution internal and maintain a lighter board with the milestones the client actually cares about. More upkeep, but total control over what they see.
Whichever you pick, remember that everything on that board is visible: card titles, descriptions, comments left on cards, and who's assigned. Put internal snark somewhere else.
Making the board readable for someone who isn't you
A board that makes sense to your team can be noise to a client. A few adjustments go a long way:
- Name lists in client language. “Blocked” and “In review” mean something. “Icebox” and “WIP-2” don't.
- Use due dates on the things they asked about.The card face shows the date range, so “when is this landing?” answers itself.
- Write the card, not the email. Put the status update in the card description — with headings and a checklist — and the link becomes the update.
- Keep a “Done” list visible.Clients underestimate throughput. A column of finished cards is the cheapest trust you'll ever buy.
If your board is still organized for you rather than for readers, our guide to organizing projects with kanban is a good place to start.
Revoking access when the project ends
Links leak. Engagements end. Both are handled from the same Share modal: turning the public link off makes the URL return a 404 immediately, and regenerating it mints a new URL while invalidating the old one — useful when a link was forwarded somewhere it shouldn't have been. There's no cleanup of guest accounts afterward, because there were never any accounts.
When a client should be a real member instead
Read-only links are for visibility. When a client needs to actually participate — approving work in comments, being @mentioned, getting notified — invite them as a member instead. Decknote has two roles: Viewer for someone who should only read inside the app, and Editor for a client who needs to comment and be part of the conversation. Either way members are free: up to 10 per board on the free plan, unlimited on Pro, with no per-seat charge.
That's the part that changes the math for client work. Because Decknote Pro is $5 per month flat per board owner — not per user — the person paying is you, once, and every client you bring onto a board comes along at no extra cost. Compare that with $5 to $12 per person per month elsewhere; see the pricing page for the full breakdown.
The short version
- Public read-only link for clients who just need to look.
- Editor membership for clients who need to comment.
- One board per client keeps the boundary obvious.
- Turn the link off or regenerate it when the project ends.
Create your free Decknote account and try all of this on your own board — no credit card required.