Field notes

Public Vs
Private Help Center

Public help centers reduce repetitive questions and improve discoverability. Private help centers support onboarding, implementation, and account-specific workflows. Most serious support teams need both in one platform.

Start a free trialSee pricing
Shared support inbox with customer context, AI draft, and source panels
Jump to
All postsProblem guidesAlternativesDocs
Sections
3
Scannable chunks so the page works as a quick-reference guide.
Published
2026-03-30
Current editorial baseline for this version of the playbook.
Intent
Operator
Written for support leads, docs owners, and implementation teams.
Quick read
The short version of what this post gives the team.
Who it is for
Support leads and docs owners

When to publish content publicly, when to gate it, and why most support teams need both.

What you leave with
3 practical sections

This page is structured so the team can scan, decide, and act without reading a generic long-form essay.

Best follow-up
Turn the playbook into pages

After reading, move into related problem pages or comparisons and turn the strongest topics into docs and SEO assets.

Article
When to publish content publicly, when to gate it, and why most support teams need both.

01. Public docs should answer common pre-ticket questions

Your public help center is where search engines, AI crawlers, and customers discover the basics. This content should be easy to find, easy to trust, and written around repeatable tasks or issues.

02. Private docs protect account-specific knowledge

Implementation details, account workflows, and advanced instructions often belong behind access controls. Keeping them in the same product as the public help center reduces duplication and authoring overhead.

03. The authoring model should stay consistent across both

One structure, one search model, and one support flow is easier to maintain than splitting public and private knowledge across separate tools.

Keep reading
Related blog posts and high-intent support pages.