Private does not mean current
Restricting access solves visibility, not the missing owner or overdue review.
Internal documentation
Publish internal runbooks, technical decisions, onboarding, and operating procedures with access controls and visible responsibility.
The operating problem
Restricting access solves visibility, not the missing owner or overdue review.
Runbooks, decisions, and onboarding notes become difficult to find and harder to verify.
An agent-generated edit or casual correction should not silently become operating policy.
The workflow
Make internal answers findable without removing the controls that make them trustworthy.
Restrict published documentation to authorized readers on Pro and higher plans.
Separate reading, writing, reviewing, publishing, and administrative actions.
Keep changes in drafts and Git history with comments and approval.
Use SAML or OIDC when configured for an Enterprise workspace.

What changes