Sharing a Kanban Board With Someone Outside Your Team

A task board is most useful to a client when they can actually see it, not when you're exporting a screenshot every Friday. Editor's kanban boards support sharing with people outside your own workspace, so a client, contractor, or partner can follow a project's status without you maintaining a second copy of it somewhere they have access.

Sharing a board

Open the board you want to share and use its share option — this opens a dedicated sharing dialog rather than reusing the general workspace-invite flow, which matters because a client shouldn't get the same access as an internal teammate by default. From there you generate access for the person you're sharing with, scoped to that specific board rather than your whole workspace.

Before you send an invite, check exactly what level of access you're granting. Editor's board sharing supports different permission levels, and the right one depends on the relationship: someone you want commenting and moving their own cards needs more access than someone who should only be able to see status. Confirm the specific levels available in your workspace's sharing dialog before assuming a client can (or can't) do something — the exact permission tiers are worth verifying against what the dialog actually offers rather than guessing from how other tools name theirs.

What the other person sees

Once shared, an outside collaborator sees the board itself — columns, cards, whatever detail your permission level exposes — without needing access to anything else in your workspace. They aren't pulled into your CRM, your other boards, or your team's internal boards; the share is scoped to the one board you granted.

Keeping track of activity

Boards you've shared outward carry an activity feed showing what's changed — cards moved, comments added, status updates — so you can see what an outside collaborator has done without having to ask them directly or compare screenshots over time. That's particularly useful once a board has more than one outside party on it: instead of reconstructing who did what from memory, the feed gives you a record.

Before you share

A board you're about to share with someone outside your team is a good moment to check what's actually visible on it — old cards from an unrelated project, internal notes in a card description, anything you wouldn't want a client reading. Sharing is scoped to the board, but everything on that board comes along with it.