Help Center

Board Visibility Settings

Control exactly who can find, view, and edit each board — from a private skunkworks project to a public roadmap.

4 min readUpdated May 2026

Overview

Every board has one of three visibility levels. The default is set at the workspace level but you can override per board, and you can change visibility at any time.

https://gryphin.app/boards/q2-roadmap/share
Board visibility
Private
Only invited members
Workspace
Everyone at Acme can join
Public
Anyone with the link, read-only
The share dialog — pick a visibility level, optionally generate a public link.

The three visibility levels

Private

Only members you explicitly invite can see this board exists. Best for HR, finance, or confidential planning.

Workspace

Everyone in your workspace can find and join this board. The default — best for everyday team work.

Public (read-only)

Anyone with the link can view but not edit. Great for public roadmaps, open-source planning, or community boards.

Changing visibility

1

Click Share

Top-right of any board.

2

Pick the new level

Each option previews exactly who will gain or lose access.

3

Review the access list

Gryphin shows a diff: people gaining access in green, losing it in red.

4

Confirm

Change takes effect immediately. People losing access get an optional courtesy email.

⚠️
Warning
Switching from Private to Public exposes the entire board to anyone with the link. Audit card titles, comments, and attachments first — sensitive info can leak.

Best practices

Private by default for sensitive

HR boards, exec planning, M&A — keep these on Private and invite per-person.

Workspace for everyday

Most boards should be discoverable. Hidden work is duplicated work.

Public for transparency

A public roadmap board is one of the highest-trust signals you can give customers.

Audit before going Public

Move sensitive cards to a private board first. Once a public link is out, you can't un-share.

Need finer control?

Business plans add per-board overrides — set a board to "Workspace-visible" but lock editing to a specific team.

Custom roles (Business)

Was this article helpful?

Let us know how we can improve