Documentation Visibility Model

Summary

Visibility classifies who may discover and read a page. It does not replace repository, portal, or identity access controls.

Documentation, product, security, engineering, partner, and customer enablement teams

Value	Intended readers	Content boundary
`public`	Anyone	Public-safe product, architecture, integration, and support information
`customer`	Authorized customers	Customer-specific operating and implementation guidance without cross-customer data
`partner`	Authorized delivery or integration partners	Partner enablement and controlled implementation material
`internal`	Authorized workforce	Internal process, ownership, planning, and non-public architecture information
`restricted`	Explicitly approved named groups	Security-sensitive, regulated, confidential, or tightly controlled operational content

Choose the most restrictive applicable classification.
Public pages must not depend on inaccessible pages for essential instructions.
Metadata and search results must not leak restricted titles, descriptions, keywords, or graph edges.
AI and automation must preserve or raise visibility, never downgrade it automatically.
Moving content to a less restrictive class requires security and owner approval.
Customer and partner content requires audience isolation and approved distribution controls.
The legacy confidential value maps to restricted during migration and remains validator-compatible temporarily.