Multi-Site Documentation: Many Sites, One Source | ClickHelp
Back
to top
Multi-Site Documentation

Separate your Documentation Sites. Keep one source behind them.

Give products, brands, and markets independent Documentation Sites while shared content and the authoring team stay together. Use separate portals when data or teams need full isolation.

Request Demo Start Free Trial
See how it works Compare The Options
One ClickHelp portal · one team, one set of permissions
docs.product-a.com GUIDE
SECURITY
docs.product-b.com API
GET
POST
PUT
docs.product.de DE
SECURITY
The Trade-Off

Separation and reuse pull in opposite directions

Every setup ends up on one side of that line, and pays for it on the other.

Everything in one pile

A wiki, local folders, the support help center or PDFs. Nothing to separate brands and audiences with, and no single source.

Split into islands

Every product got its own isolated unit. The content, team and permissions split with it, so shared material is maintained twice.

Separation lives in the repo

Separate repositories and builds. Every change, and even a review, waits on the engineering cycle.

Separation by copy-paste

Copies of the same guide per product, market and customer. Discrepancies surface after publication.

In their own words
“We don't want a public site where client A and client B can find each other's knowledge bases.”
Documentation Manager · B2B SaaS
“It's very hard to manage four or even more different products inside one help center.”
Documentation Owner · Adtech
The common problem

What readers need separated should not force your team to duplicate content.

ClickHelp lets you decide separately what readers see and what authors share.

How ClickHelp handles it
HOW CLICKHELP HANDLES IT

Separate what readers see. Keep together what your team writes.

Use Documentation Sites where content and teams should stay shared, and separate portals where isolation is required. Combine both when you need both.

One portal, several Documentation Sites

The same three sites, all served from one portal.

Shared content and team
Topics, snippets, variables, translations, permissions
docs.product-a.com
docs.product-b.com
docs.product.de

Separate portals

The same three sites, split across two portals.

EU portal
Own content and team
docs.product-a.com
docs.product-b.com
US portal
Separate content and team
docs.product.de
Ian Avilov
Ian Avilov · Product Manager, ClickHelp · LinkedIn
Recommendation from the ClickHelp team

Choose the boundary that matches what actually needs to be separate.

Where you draw the boundary shapes your documentation process, not just your URLs: who reviews what, whose terminology governs a section, and which team owns a shared block. For large teams the answer is usually a combination — a portal per division, several Documentation Sites inside each.

It also decides how well AI works for you. A narrow context is better on both ends — the writing assistant checks against one product's terminology instead of averaging across the portfolio, and the reader assistant stops confusing products and versions.

What you need apart How you set it up What stays shared
A brand and domain per product or market A Documentation Site per brand: its own domain, theme, Reader UI and interface language, its own Home, Login and 404 pages, and its own selection of published content. Everything authors touch — topics, snippets, variables, conditions, translations, users and permissions.
Audiences on the same site Roles and access rules, so partners, resellers, individual customers and internal teams each see only what is meant for them. Configured by the documentation team, without IT. All of it — one set of content, filtered per role rather than copied per audience.
Data, teams and permissions between divisions Separate portals — for data that has to live apart by region, teams that must not overlap, or different email notification templates. Nothing, by design. This is the isolation option, and it is the right one when isolation is the actual requirement.
Single-Sourcing

More sites should not mean more work

Separation only pays off if the split content stays governable from one place.

One source, every site that uses it
SECURITY
Edit it here
once, in one place
docs.product-a.com
docs.product-b.com
docs.product.de

Every site pulls the section in by reference, so it updates everywhere at once — no copies to chase.

Everything that keeps many sites manageable by one team
Versions per product and market

Each site publishes the version its audience is on.

Conditional content per deployment

Output tags assemble a per-customer guide with no separate copy.

Search scoped to each site

Synonyms and tags follow that brand’s vocabulary; results stay isolated.

API reference from the build process

Developer docs update on their own site, outside the writing cycle.

Context help inside each product

Every product calls its own site from its own UI.

Analytics per site, in one place

Reader behavior compared across brands and markets in one report.

See it on your setup

Bring your product list, we will map it to sites

See how this setup would work for your products, brands, or markets.
Request Demo
Compare The Options

Where the trade-off actually shows up.

Different tools solve different jobs well. The trade-off appears when one team needs multiple independent Documentation Sites without duplicating shared content or splitting the team.

Separate sites without separating content and team

ClickHelp is the only option here that does both. Open any pairing below to see where the others stop.

ClickHelp vs Team wikis
CH
WIKIS
Separate sites with their own domain and branding
Separate sites without separating content and team
Separate sites without separate accounts
One source of content across all sites
Role-based audience separation inside a site
Partial
Review and commenting in the browser
Setup and publishing without developers
Migration from external systems
Partial
ClickHelp vs Support help centers
CH
HELP C.
Separate sites with their own domain and branding
Partial
Separate sites without separating content and team
Separate sites without separate accounts
Partial
One source of content across all sites
Role-based audience separation inside a site
Partial
Review and commenting in the browser
Partial
Setup and publishing without developers
Migration from external systems
Partial
ClickHelp vs Desktop HAT
CH
HAT
Separate sites with their own domain and branding
Partial
Separate sites without separating content and team
Partial
Separate sites without separate accounts
One source of content across all sites
Role-based audience separation inside a site
Review and commenting in the browser
Setup and publishing without developers
Partial
Migration from external systems
Partial
ClickHelp vs Dev doc generators
CH
DEV GEN.
Separate sites with their own domain and branding
Separate sites without separating content and team
Separate sites without separate accounts
One source of content across all sites
Partial
Role-based audience separation inside a site
Review and commenting in the browser
Setup and publishing without developers
Migration from external systems
Partial
ClickHelp vs Isolated per-product units
CH
UNITS
Separate sites with their own domain and branding
Separate sites without separating content and team
Separate sites without separate accounts
One source of content across all sites
Role-based audience separation inside a site
Partial
Review and commenting in the browser
Setup and publishing without developers
Migration from external systems
Partial
Capability ClickHelp Team wikis Support help centers Desktop HAT Dev doc generators Isolated per-product units
Separate sites with their own domain and branding Partial Partial
Separate sites without separating content and team Partial
Separate sites without separate accounts Partial
One source of content across all sites Partial
Role-based audience separation inside a site Partial Partial Partial
Review and commenting in the browser Partial
Setup and publishing without developers Partial
Migration from external systems Partial Partial Partial Partial Partial
Before You Commit

Three things worth settling before you move

What survives the move

Structure, images and formatting carry over. From desktop help-authoring tools, snippets, variables, conditional tags and the table of contents come across — proven on production projects.

From team wikis, excerpt macros become snippets. From Word, the reuse logic is set up fresh, because the source does not carry any.

Who owns the setup

Sites, themes, custom pages, publications and access are configured by the documentation team in the interface. A custom domain is optional — a Documentation Site works on the platform domain. If you want your own, delegating it is a one-time action on the IT side, not a standing dependency on the engineering cycle.

PS
“For us, it's critical to know: if we export our current pages from Confluence to a new platform, will it completely retain the structure, images, and formatting without us losing anything?”
Patrick Sherman · Documentation Manager

Where the boundaries go

Which sites and portals your structure actually needs, what stays shared, and how the content you have maps onto that. We work with distributed, multi-product teams and can go through your case together.

Discuss your setup
Recognized on G2 in Help Authoring Tools

Rated by the documentation teams who use it every day.

G2 Leader — Winter 2025 G2 Easiest to Use — Winter 2025 G2 Best Usability — Winter 2025 G2 Best Support — Quality of Support G2 Users Most Likely to Recommend — Fall 2024
SOC 2 Type II
Audited controls
GDPR & CCPA
Compliant processing
SSO, RBAC, AES-256
Access and encryption
99.5% uptime SLA
With backups
Patented full-text search
Scoped to each site
PLANNING YOUR SETUP?

Not sure how to structure docs for several products?

Most teams aren't, and the right answer depends on what actually needs to be apart — products, brands, markets or audiences. On the call we go through your case and lay out how it maps to Documentation Sites, portals and roles. Then try it on your own content.

Discuss Your SetupStart Free Trial
No credit card Full feature access Cancel anytime
WHAT WE'LL WORK OUT
  • Which products get their own site
  • Where separate portals make more sense
  • What stays shared across all of them
  • How partners and clients see only theirs
  • What your current docs carry over
Ask AI about ClickHelp
ChatGPT ChatGPT Claude Gemini Grok Perplexity