Documents
Public Libraries
Public Libraries
Type
Document
Status
Published
Created
Jun 16, 2026
Updated
Jun 22, 2026

A Library is private by default. Setting its visibility to public lets anyone read its Documents and ask questions. This page explains the difference between a public and a private Library, how to make one public, what unauthenticated visitors can see, and how this applies to open source projects and public community knowledge.

Public versus private#

Every Library has a Visibility setting with two values.

  • Private (the default). Only members of your organization can open the Library, read its Documents, and ask questions. This is the right choice for internal knowledge: service docs, runbooks, architecture, anything you would not publish.
  • Public. Anyone with the link can read the Library and ask questions, including people who are not signed in and do not have a Dosu account. Public Libraries are meant for open source projects and public knowledge sites.

Visibility is set per Library, so you can keep most of your knowledge private while opening up one Library (for example, a public-facing product or an open source repo) without changing anything else.

Important: when a Library is public, everything in it is public. All Documents and their connected Sources become queryable by anyone. Treat a public Library as a publishing surface, and connect only Sources whose content is safe to expose.

Why it matters#

Open source projects face the same knowledge problem as private codebases. Answers live in issues, pull requests, and discussions, and they are hard for users and new contributors to find. A public Library turns that activity into documentation people can read and a place where anyone can ask a question and get a grounded answer, which takes the load off maintainers.

For companies, a public Library is community knowledge powered by the same engine you already run internally. You can maintain a public help center or developer docs site that stays up to date as your project evolves, while your private Libraries keep internal knowledge restricted to your organization. One setup, two audiences.

How to make a Library public#

  1. Open the Library you want to publish from Libraries. You can also choose visibility while creating a new one at create a Library.
  2. In the Library settings, find Visibility and switch it to Public.
  3. Confirm. Dosu shows a warning that public Libraries can be accessed by anyone with the link and that all content will be visible to the public.
  4. Once it is public, Dosu gives you a Public Library URL. Share that link to give people read and ask access. To make the Library private again, switch Visibility back to Private.

Only owners and admins can change a Library's settings. See Roles and RBAC.

Open source repositories#

If you maintain or contribute to a public GitHub repository, you can publish it as a public Library without building one by hand. Using the dosu CLI, run:

dosu add owner/repo

Prerequisites:

  • The dosu CLI is installed.
  • You are authenticated with GitHub (gh auth login).
  • The target repository is public on GitHub.

What visitors can see#

On a public Library, an unauthenticated visitor can:

  • Browse the Library's Documents.
  • Ask questions and get answers grounded in the Library's Sources, including code, issues, pull requests, and discussions.

Visitors are readers. Publishing a Library does not give the public the ability to edit Documents, change settings, or see your other (private) Libraries. Drafting, Review, and configuration stay with your organization's members.

Discovery#

Public Libraries are discoverable as well as shareable.

  • Browse public Libraries at https://app.dosu.dev/explore.
  • For a GitHub repository, swap github.com for github.dosu.com in the URL to jump straight to its public Library. For example, https://github.com/apache/airflow becomes https://github.dosu.com/apache/airflow. If no public Library exists for that repository yet, the page offers a way to request one.

Notes and limits#

  • Public visibility exposes the whole Library. There is no per-Document or per-Source public toggle, so split anything sensitive into a separate private Library.
  • Web is a real-time Source. Dosu reads the web at query time and does not crawl, index, or store website content, so making a Library public does not publish a crawl of any site.
  • Visibility is reversible at any time. Switching back to Private immediately restores organization-only access.
Public Libraries | Dosu