# Zuwiki ## Public vs Internal Wikis > Category: Access & Sharing --- ## Pages - [Welcome to Zuwiki](https://docs.zuwiki.com/welcome-to-zuwiki) ### Getting Started - [Create Your First Wiki](https://docs.zuwiki.com/getting-started/create-your-first-wiki) - [Organize with Categories](https://docs.zuwiki.com/getting-started/organize-with-categories) - [Publish Your First Page](https://docs.zuwiki.com/getting-started/publish-your-first-page) ### Core Concepts - [Wikis, Categories, and Pages](https://docs.zuwiki.com/core-concepts/wikis-categories-and-pages) - [Page Lifecycle](https://docs.zuwiki.com/core-concepts/page-lifecycle) - [Page History and Restore](https://docs.zuwiki.com/core-concepts/page-history-and-restore) ### Access & Sharing - [Public vs Internal Wikis](https://docs.zuwiki.com/access-sharing/public-vs-internal-wikis) - [Visibility for Public Wikis](https://docs.zuwiki.com/access-sharing/visibility-and-access) - [Share Links](https://docs.zuwiki.com/access-sharing/share-links) - [Access Grants](https://docs.zuwiki.com/access-sharing/access-grants) - [Classification and Sensitivity](https://docs.zuwiki.com/access-sharing/classification-and-sensitivity) ### Editor Guide - [Markdown Basics](https://docs.zuwiki.com/editor-guide/markdown-basics) - [Linking Between Pages](https://docs.zuwiki.com/editor-guide/linking-between-pages) - [Icons and Visual Touches](https://docs.zuwiki.com/editor-guide/icons-and-visual-touches) - [Rich Content Blocks](https://docs.zuwiki.com/editor-guide/rich-content-blocks) - [OpenAPI Pages](https://docs.zuwiki.com/editor-guide/openapi-pages) ### Plans & Account - [Plans and Limits](https://docs.zuwiki.com/plans-account/plans-and-limits) - [Custom Domain](https://docs.zuwiki.com/plans-account/custom-domain) - [Zuwiki for Open Source](https://docs.zuwiki.com/plans-account/zuwiki-for-open-source) ### Integrations - [MCP Server](https://docs.zuwiki.com/integrations/mcp-server) --- # Public vs Internal Wikis Every wiki in Zuwiki has a **mode**, and the mode is the first decision you make when you create one. It decides where the wiki lives, who can reach it, and which features apply. There are two modes: **Public documentation** and **Internal knowledge**. Pick the mode by what the content is for, not by how sensitive one page feels. Sensitivity inside an internal wiki is handled separately, see [Classification and Sensitivity](/access-sharing/classification-and-sensitivity). ## Public documentation A public wiki is meant to be read on the web. It is served on its own public host, keeps the full Zuwiki design, and can run on a [custom domain](/plans-account/custom-domain). - Access is governed by **visibility**: open to everyone, organization members only, a password, or a verified email domain. See [Visibility for Public Wikis](/access-sharing/visibility-and-access). - You can hand out [share links](/access-sharing/share-links) to let specific outsiders past a gate without an account. - Extras like a custom OpenGraph image and external analytics apply here. - There is no classification, no audit log, and no watermark. A public wiki is a website. Use this mode for product docs, API references, help centers, changelogs, anything whose natural home is a public URL, even if you keep it gated for a while. ## Internal knowledge An internal wiki is for your organization only. It is **never served publicly**. Members read it inside the app in a neutral reader, not on a branded public site. - Access is governed by **teams and people**, not by a public visibility setting. Every organization member can read it by default, and you can narrow that down. See [Access Grants](/access-sharing/access-grants). - It can carry a **classification**. Confidential and Restricted content is watermarked with the reader's email and every read is recorded in the audit log. See [Classification and Sensitivity](/access-sharing/classification-and-sensitivity). - Public features such as custom domains, share links, public visibility, and OpenGraph images do not apply. Use this mode for onboarding notes, runbooks, internal decisions, HR material, security playbooks, anything that should stay inside the company. ## At a glance | | Public documentation | Internal knowledge | | --- | --- | --- | | Where it is served | Public host, optional custom domain | In app reader only | | Who can read | Controlled by visibility | Controlled by teams and people | | Reach outsiders | Yes, via visibility or a share link | No | | Classification, audit, watermark | No | Optional | | Custom design, OpenGraph, analytics | Yes | No | ## Choosing and changing the mode You choose the mode when you create a wiki, as a choice between **Public documentation** and **Internal knowledge**. You can change it later in the wiki settings under **Security**. Switching is guarded so content cannot leak by accident: - Moving a public wiki to internal turns its visibility into organization members only and clears any password or email domain. - Moving an internal wiki to public resets it to fully public visibility and clears its access restriction. If the wiki is classified as Confidential or Restricted, lower the classification to Internal first, otherwise the switch is blocked. When in doubt, start internal. Opening a wiki up later is one switch, and you will not have published anything by accident in the meantime.