Publishing & Visibility

Every documentation page has a visibility setting that controls who can read it. By default, pages are private. You change a page's visibility from its actions menu in the Docs editor.

Visibility levels

Setting a level can cascade to all descendants of a page, so you can publish a whole subtree at once. To revoke, set the page back to a more restricted level.

Public pages

When a page is public, an anonymous visitor opening its link sees the page content, the public navigation tree, breadcrumbs, and search across public pages — but not authors, version history, comments, or any edit controls. Private pages return "not found" to anonymous visitors (their existence isn't revealed). Sensitive content is the author's responsibility — the page is published as written.

Good uses for public pages: onboarding material, a public API reference, an open roadmap, a changelog.

Trusted-workspace pages

The trusted level lets members of another workspace read a page without making it public to the internet. It relies on the same one-way trust you manage in Workspace Settings → Trusted Workspaces: if your workspace trusts workspace B, B's members can read your trusted (and public) pages. Trust is asymmetric — trusting B does not let you read B's pages.

Tip: visibility is set per page (with optional cascade), so you can keep a private tree and expose just the branch you intend to share.