Understanding ClickHelp

ClickHelp is a cloud-based documentation solution designed for technical teams that need to publish and maintain knowledge bases, user guides, and developer docs across multiple formats. At its core, ClickHelp enables Single source of truth for content, reusing snippets, variables, and conditional content to ensure consistency across portals, PDFs, and API-friendly outputs. This conceptual overview explains what makes ClickHelp different and how the onboarding journey is structured to get you from zero to a branded, searchable documentation portal quickly.

What makes ClickHelp unique

ClickHelp differentiates itself through a combination of five capabilities that work together to simplify authoring, publishing, and governance. Each differentiator below is explained with concrete implications for your team and workflows.

Single-sourcing across formats

With Single source of truth, you author content once and reuse it across formats and audiences. Snippets, variables, and conditional content enable you to tailor output without creating drift. For example, you can maintain a single user guide topic and publish it as both a web article and a PDF manual, with audience-specific sections appearing or hidden automatically based on your target output.

Brandable portals with granular access

ClickHelp includes Portal templates and extensive branding options—six ready-made templates, CSS customization, and a custom domain. You can configure access controls on a per-portal basis and integrate SSO for enterprise security. This makes it possible to deliver external knowledge bases to customers while keeping internal docs private or brand-consistent for partners.

AI-assisted authoring

The editor features AI-assisted authoring, which helps you draft, suggest improvements, and ensure consistency with your terminology. AI-ready outputs like llms.txt and WriteAssist are embedded in the editor, enabling you to prepare context-rich content for AI agents or external tools while preserving exact citations from your content sources.

MCP server integration

Our MCP server context delivery provides structured content and context to AI agents. This enables precise retrieval and citation when readers use in-app AI search or external AI tools, reducing the risk of hallucinations and drift in auto-generated answers.

Native integrations and extensibility

ClickHelp ships with extensive native integrations (20+) and supports CI/CD workflows, analytics, and third-party tools. This includes GA4, Zapier, Zendesk, Salesforce, and API access for automated publishing. The result is a streamlined lifecycle where content moves from authoring to published outputs with governance and traceability.

Core concepts in practice

Throughout this topic, you will encounter several core concepts. They are defined in popups the first time you see them so you can reference them without leaving the page.

llms.txt is a machine-readable file that points AI tools to where content lives for citing and retrieving context. Single source of truth means you write once and reuse content across editions and reader portals. Topic-based authoring organizes content into modular units that can be published independently. MCP server delivers a structured context feed to AI agents. Conditional content lets you tailor outputs to audience, edition, or format. Finally, Portal templates provide quick-start layouts that you can brand and customize.

To help you orient, the onboarding journey defines the sequence of actions you’ll take. We’ll map each step to the tasks you need to complete and show you what you gain after each milestone.

Who this is for

This guide is written for Technical writing teams, Documentation managers, and Product teams needing developer/API documentation. If your goal is to deliver branded portals, enable self-service content, and govern content at scale with secure access, you’re in the right place.

What to do next

Tip: Your portal can start with a default template and branding. You can replace the styling with CSS or switch templates anytime, but plan branding decisions early to ensure consistency across all outputs.