Publish a Knowledge Base

Public access turns a Knowledge Base into a read-only website. Anyone with its address can read the pages without signing in. The people and agents who can change the source files still follow your existing roles.

What becomes a page

The public site reads Markdown from the Knowledge Base's wiki/ folder:

• wiki/README.md is the home page.
• Other Markdown files inside wiki/ become pages when every folder and filename segment uses lowercase letters and numbers separated by single hyphens. A folder README.md becomes that folder's page. Names used by built-in public routes are reserved and do not become pages.
• wiki/nav.yaml sets the page order and groups shown in the Menu. It configures the site and is not itself a page.
• A published page can include a permitted asset from anywhere in the same Knowledge Base by referencing its exact relative path. Referenced assets join the public collection; unreferenced assets stay outside it unless an owner explicitly includes their folder. Atmina serves supported images as resized copies with location data removed, never the original file.
• Public image publishing must be available in your Atmina environment. Unsupported picture types and unavailable transformations keep their image label as a fallback. Other non-page files are not served, so keep essential information in Markdown text.

Published pages keep the order from wiki/nav.yaml. Previous and Next links follow that order, including the home page. On wide screens, On this page links take readers to the second- and third-level headings in the current page.

On a small screen, the menu icon opens navigation over the page, with Appearance choices at the bottom. On wider screens, use Theme at the right of the header. Choose Light, Dark, Yellow, or System. Changing the theme reloads the page and remembers your choice in this browser for public pages on the same site. System follows your device’s light or dark setting.

Every page has a View as Markdown link in its footer. Page addresses ending in .md return a public projection of the Markdown; the home page uses /index.md. Links and available images use absolute public addresses so they work independently of where an agent fetched the text. Missing or private images keep their alt text without exposing a file address, and external images become links. The projection keeps source line numbers stable. The footer links to llms.txt, the page index for agents; llms-full.txt provides the published pages together. Connect via MCP opens connection instructions for this specific Knowledge Base, including its anonymous search endpoint. The small Powered by atmina, Atmina Terms, and Atmina Privacy links identify the hosting product and its policies. Public Knowledge Bases do not have the Guide's /docs search page.

Make the site public

You need to be an administrator of the team that owns the Knowledge Base. Public access is unavailable while the Knowledge Base has a connected source, so disconnect its sources before publishing.

1. Open the Knowledge Base in Atmina and select Sharing.
2. Review the Public collection preview. The default includes published pages and permitted assets those pages reference.
3. If you need a broader collection, enter ordinary folder paths under Additional folders, or enable Include source mirrors or Include promoted outputs. Select Review collection to see the server-checked result, then Save public collection and confirm it.
4. Turn on Public access, review the confirmation, and select Make Knowledge Base name public.

A customer's public address has the form https://atmina.ai/kb/<team>/<knowledge-base>. The Atmina Guide uses its shorter address, https://atmina.ai/docs. The same collection rules apply to both new and already-public Knowledge Bases. Broader access is always an explicit opt-in.

Turn public access off

Published pages and supported images use versioned caching to keep navigation fast. Your browser checks for the current version before reusing a page. Editing content or changing publication settings invalidates its previous cache entry.

Return to Sharing and turn Public access off. Once Atmina confirms the change, new anonymous requests cannot read the pages, search results, or assets, including through previously cached addresses. Team members keep the access granted by their roles. Copies someone already downloaded cannot be recalled.

Removing a folder opt-in or the final qualifying reference to an asset also removes that access once the change is confirmed, unless another allowed path still includes it. An unavailable public resource returns the same neutral Page not found response as an absent one.

Choose the public collection

The collection is the boundary for all anonymous access: website pages, Markdown, MCP and REST search, file reads, images, listings, and discovery. Ordinary links to another document do not publish that document automatically. Referenced assets must belong to the same Knowledge Base and pass the asset policy. Their verified Companion text can be included for safe reads and search.

Additional folders includes files beneath each selected folder. Include source mirrors adds _sources/; Include promoted outputs adds _consolidated/. These options are off by default. They broaden anonymous access, but do not turn every included file into a rendered wiki page. Markdown in an opted-in folder can reference permitted assets too.

_system/, _staged/, _pulse/, and _exports/ remain excluded, even if a page links to them. Source-mirror opt-in does not remove the restriction on publishing a Knowledge Base with connected sources.

Keep private material outside the public collection and review its preview before widening access. To decide what belongs in the published site, start with capture and recall.

Links and sources on published pages

When links between memories are enabled for the Knowledge Base, a published page distinguishes a working link, a link to the same page, a missing target, and an invalid target. Linked from and Links to list the published pages connected to the page you are reading. Only links from ordinary authored content appear in this public context. If graph extraction is still pending or the public graph response reaches its bound, the page says that some link context is unavailable instead of presenting the partial result as complete.

An evidence marker shows the evidence type and a short description without requiring JavaScript. The Sources section repeats every recorded source in its authored order. A source inside the same published collection links to its public page; an external HTTPS source links to its original address; an agent-session source exposes no private session path; and a missing in-base source stays visibly unresolved.