---
title: "Core concepts"
url: "/help/buuk/core-concepts"
updated: "2026-11-13T13:31:57.647Z"
---
# Core concepts

Buuk organizes documentation as a hierarchy: a workspace holds collections, collections hold sections, sections hold folders and articles. Learn these terms and the dashboard, the public site, and this help center all make sense.

One idea runs through everything: customers read published pages only. Drafts, AI drafts, and suggested updates stay inside the team until a person publishes them.

## The workspace

A workspace is the unit of documentation. It holds the name, the brand, the members, the plan, and one public help center. The public URL looks like `/help/your-slug` — this sample lives at `/help/buuk`. On Growth you can attach a custom domain such as `docs.yourproduct.com`.

Members have one of three roles. **Owners** manage billing, members, and domains, and can publish. **Editors** write, organize, and publish. **Viewers** read drafts in the dashboard without changing live pages.

## The hierarchy

| Term | What it is |
| --- | --- |
| Workspace | The top-level account: branding, members, plan, and one public help center |
| Collection | A tab on the public site — Documentation, FAQ, Guides, API reference, Changelog |
| Section | A top-level group inside a collection, shown in the public sidebar |
| Folder | A collapsible group nested under a section, for related pages |
| Article | A page readers open — a how-to, a short answer, or a walkthrough |
| Draft / published | Every article is one or the other. Customers see published pages only |

## Collections and tabs

A collection is a public tab. A full docs site — this workspace — turns on five: Documentation, FAQ, Guides, API reference, and Changelog. Add, rename, reorder, or remove tabs with Manage tabs in **Help Centre**. A collection with nothing in it hides its tab. See [Documentation vs FAQ vs Guides vs API](./docs-collections).

## Drafts and published

New articles, imports, AI drafts, and accepted suggestions all land as drafts. Drafts are visible to the team in the dashboard but out of public search, the widget, and Ask AI. **Preview in help center** shows you how the page will look — it does not make the draft public.

Publishing is a deliberate step. You can require editorial approval before anyone ships, or schedule a publish time. See [Review, versions, and scheduling](./review-versions-and-scheduling).

## Version history

Every article keeps version history. Open it to compare or restore an earlier snapshot if a rewrite goes the wrong way.

## Suggestions

Suggestions are a review list built from work your team already does — support tickets, Slack threads, GitHub releases, Linear issues, searches that returned nothing, and “not helpful” feedback. Open **Suggestions**, accept the ones that should become docs, edit before you publish, or dismiss the rest. Buuk never ships a suggestion on its own. See [Suggested updates](./suggested-updates).

## Access groups and locales

Access groups on a section or article restrict who can read it on the public site. An empty group means unrestricted. A private help center goes further and can use a passphrase or JWT for readers who are not members. See [Members, roles, and groups](./members-roles-and-groups).

Locales work per article. Enable languages in **Settings → Languages**. English is the source, and empty translation fields fall back to it. See [Translations](./translations).

## API tokens and MCP

In **Settings → Developers → API tokens** you can mint a `buuk_cli_` token with read-only or write access. The same token initializes MCP at `/api/mcp`, and you can enable a public MCP endpoint so external AI tools read your published docs. See [API tokens and MCP](./api-tokens-and-mcp).

## Related

- [How Buuk works](./how-buuk-works)
- [Organize sections and folders](./organize-sections-and-folders)
- [Suggested updates](./suggested-updates)
- [Members, roles, and groups](./members-roles-and-groups)
- [API tokens and MCP](./api-tokens-and-mcp)