Public Teams & Guest Access

Making a team public

Team Settings → Overview → Visibility → Public

• Private (default): only invited members see the team; others get Team Unavailable.
• Public: anyone with the URL can open Guest View.

Public teams still require sign-in for write operations—guests are read-only.

Guest experience

When isMember === false (logged out or not on roster):

UI element	Guest behaviour
Header badge	Guest View instead of plan name
Team menu	Disabled — no Settings, Change Plan, Leave
Inbox / Audit	Hidden from sidebar
Invite button	Hidden
Command palette	Search/navigation only; no admin actions
Overview	Team Preview banner
New Space	Hidden
Team Resources cards	Hidden
Content	Read-only for Public/Restricted visibility rules

What guests can read

Effective read access depends on space and page visibility:

• Public space/page on a public team — typically readable
• Restricted — may require membership even on public teams (team members only)
• Private — never visible to guests

Use cases

• Open-source or community programmes showing decision history
• Stakeholder transparency without granting edit seats
• Sharing a single public space while keeping other spaces private (Pro+ visibility)

Inviting guests as members

If someone needs to comment or propose decisions, send a normal invite—guest preview is not sufficient.

Switching between teams

Use Switch Team (/teams) or command palette to move between workspaces you belong to vs public teams you merely view.