Access control
Protect private documentation without moving authorization into page content.
Foldocs emits static files, so access control belongs at the hosting edge. Put Cloudflare Access, an authenticated reverse proxy, or an equivalent platform policy in front of every HTML, Markdown, search-index, asset, and LLM route.
Protect the complete corpus
Blocking only page HTML is insufficient. Search indexes and llms-full.txt
contain page text, while sibling .md routes expose individual documents.
Configure one policy for the whole deployment origin.
Test authorization
Verify HTML, .md, search indexes, llms.txt, assets, and not-found responses
through the protected origin. A public auxiliary route can reveal the same
content as a protected page.
Cache policy
Keep private responses out of shared public caches unless the edge platform keys its cache by authenticated policy state.
Last updated 2 ago 2026