Internal documentation

Private knowledge with ownership and a maintenance path.

Publish internal runbooks, technical decisions, onboarding, and operating procedures with access controls and visible responsibility.

The operating problem

Publishing is one moment. Accuracy is continuous.

01

Private does not mean current

Restricting access solves visibility, not the missing owner or overdue review.

02

Answers scatter across tools

Runbooks, decisions, and onboarding notes become difficult to find and harder to verify.

03

Sensitive changes need review

An agent-generated edit or casual correction should not silently become operating policy.

The workflow

One source from draft through evidence.

Make internal answers findable without removing the controls that make them trustworthy.

Private sites

Restrict published documentation to authorized readers on Pro and higher plans.

Workspace roles

Separate reading, writing, reviewing, publishing, and administrative actions.

Reviewable history

Keep changes in drafts and Git history with comments and approval.

Enterprise identity

Use SAML or OIDC when configured for an Enterprise workspace.

The Staleless visual documentation editor

What changes

Make internal answers findable without removing the controls that make them trustworthy.