Team project sharing in BoardSnap — not yet, but here's how teams work around it.

## The current situation

BoardSnap projects are private to the account that owns them. There is no invite link, no access management panel, and no way to give a colleague read or write access to your project today.

This is the biggest gap for team use, and it's on the product roadmap — but it has not shipped.

## What teams do today

Despite the lack of native sharing, teams use BoardSnap effectively with a few patterns:

Pattern 1 — One designated snapper. One person owns the BoardSnap account for a given project or team. They snap every board, and the project builds up context and history over time. They export action items after each meeting and paste them into the team's tools.

Pattern 2 — Everyone snaps, everyone exports. Each person has their own account. After a meeting, whoever snapped the board exports the action item list and shares it to Slack or Notion. No shared project needed when the output lands in a shared place.

Pattern 3 — Share the summary link. BoardSnap's share sheet lets you send the generated summary and action items as text. Paste into a shared Slack thread, a Notion page, or a meeting document that the whole team can see.

## What team sharing would look like

When project sharing ships, the most useful version would allow multiple accounts to view boards, action items, and summaries in a shared project — and ideally assign action items to team members by name. Nothing like that exists today.

## Keeping your team informed

If team sharing is a blocker for your workflow, let us know at [email protected]. Every signal about how teams want to use BoardSnap shapes what gets built next.