---
title: "Private help centre"
url: "/help/buuk/private-help-centre"
updated: "2026-10-22T11:13:38.646Z"
---
# Private help centre

Help centers are public by default: anyone with the URL can read them. A private help center still exists as a site, but only readers who can prove access get past the front door.

Private help centers are for internal runbooks, customer-only FAQs, and docs you sell access to. Private sites stay off public search.

## Switch visibility and reader access

Open **Settings → General** and find the **Help center access** panel. The **Visibility** select switches between Public and Private, and takes effect when you save.

**Reader authentication** decides how a private site unlocks. There are three modes:

- **No reader login **— private, with a members-only notice for visitors.
- **Shared passphrase **— readers type a passphrase you set and share.
- **Signed JWT / magic link **— readers open a signed link your systems generate, or paste a token.

Passphrase and JWT secret fields are write-only: Buuk never shows you the value again, and entering a new one rotates it. JWT mode requires a signing secret of at least eight characters before the save succeeds. Private help centers arrive with Enterprise, alongside SAML SSO and SCIM.

## Who can read what

Signed-in workspace members — owners, editors, viewers — can always read their own workspace's help center. Everyone else passes the gate by passphrase or token.

Signed tokens can carry extra claims, such as `role:eng` or `tier:paid`. Access groups match on one claim key and value; passphrase readers carry no claims. Restrict a section or an article to groups from the dashboard — a page restricted to a group only opens for a reader whose token satisfies every required group's claim. Empty group restrictions mean unrestricted.

Each article also has a per-page visibility, set from its page settings under **Listed in**. It controls where the page turns up:

| Visibility | Where readers find it |
| --- | --- |
| Everywhere | Sidebar, search, and AI assistant |
| Unlisted | Hidden from the sidebar; still in search and AI |
| Direct link only | Not in sidebar, search, or AI |
| AI assistant only | Answer material; readers can’t open it |

> [!NOTE]
> AI-only pages ground Ask AI answers without appearing in the nav — useful for legal or support policy you do not want sitting in the sidebar. See [Search and Ask AI](./search-and-ask-ai).

## What readers experience

A gated reader who opens a private help center is redirected to a branded access page. Passphrase mode shows a passphrase field; JWT mode offers a signed access link and a field to paste a token. Access without credentials — no reader login mode — shows the members-only notice with a sign-in option.

Clear error messages accompany a failed attempt: a wrong passphrase, an expired or invalid access link, or a site that is private with no reader access configured yet. Once a reader passes, a signed access cookie keeps them verified on that device for 30 days; then they re-verify.

Restricted content never leaks sideways: pages that fail the current reader's group checks stay out of the sidebar, search, the widget, the public API, and AI retrieval.

## Related

- [**Members, roles, and groups**](./members-roles-and-groups) — access groups and who manages them.
- [**Search and Ask AI**](./search-and-ask-ai) — what readers can search, and AI-only answers.
- [**Publish your help center**](./publish-your-help-center) — public versus private, at a glance.
- [**SSO**](./sso) — Enterprise sign-in for your team, alongside private access.
- [**Plans and billing**](./plans-and-billing) — where private help centers sit in the plans.