Overview
Helpin Docs is the knowledge layer of the workspace: an internal knowledge base for your team and, when you want it, a public help center for your customers. Documents live in spaces, are organized with collections, and can be drafted, reviewed, versioned, and published — all in one editor.
Core concepts
Space — the top-level container in Docs. A space is internal (team-only knowledge) or external-capable (eligible to publish a public help center). Spaces can be workspace-wide or restricted to specific teams, and have a configurable review cadence.
Collection — folders inside a space that group related documents. Collections nest up to two levels deep and can be reordered by drag and drop.
Document — the primary object. A document has a status (draft, published, or archived), an owner, tags, an icon, and a full revision history.
Blocks — content inside a document is stored as addressable blocks, which is what makes per-block comments, links, and AI edits possible.
The Docs home page
Open Docs from the workspace sidebar to land on the Documentation page. From here you can:
Browse every space you have access to, with its collections and documents shown inline.
Jump into Recent documents and My documents views from the Docs rail.
Search across all documents from the docs header search.
Create a new space (pencil-and-template picker included) or a new document.
Use Arrange mode to reorder spaces and collections by dragging.
How content is structured
Workspace
└── Space (internal or external-capable)
├── Collection (level 1)
│ └── Collection (level 2)
│ └── Documents
└── Documents directly in the space
Every document belongs to exactly one space and optionally one collection.
Spaces have a visibility (workspace-wide or team-only) and a type (internal or external-capable).
Collections group documents and nest up to two levels deep — deep enough for sections like "Support → Support Inbox", shallow enough to stay navigable.
What you can do in Docs
Organize knowledge in spaces (internal or external-capable) and nest collections up to two levels deep.
Write with a rich editor — callouts, tables, toggles, code blocks, images, videos, Excalidraw whiteboards, and task lists.
Connect docs to work: embed PM tasks and epics, CRM deals and contacts, and support conversations directly inside a document, or link a doc to any object.
Draft and publish with status tracking, review schedules, and full version history with restore.
Let AI agents contribute — agents can author AI-generated sections and submit change proposals for human review.
Publish chosen spaces to a branded, searchable, multilingual public help center with custom domains and SEO.
Import existing content from Help Scout or a Nextra-based help center, redirects included.
Where Docs connects to the rest of Helpin
PM — documents link to epics, tasks, objectives, and sprints; PM objects can embed documents.
CRM — deals, contacts, and companies can link to docs (proposals, briefs, call notes).
Support — the AI support agent reads your docs to answer customers, and Coverage Gaps points back at missing documentation.
Automation — flows can create or update documents, and agents can author or propose doc changes.
How this section is organized
Docs Workspace — spaces, collections, documents, drafts & publishing, recent views, and version history.
Editor Features — everything you can put in a document and how collaboration works.
Permissions & Access — who can read, edit, publish, and administer docs; sharing and module access.
Help Center — publishing articles publicly, branding, search, localization, SEO, and redirects.
Imports & Content Migration — bringing existing documentation into Helpin.
Next steps
Head to Spaces to set up your first space, or Documents & the editor to start writing.
Was this article helpful?