Files & storage
Set up Document360
Connect a Document360 knowledge base — every published article across the project's versions becomes a document carrying its category path, so the help centre the team already writes answers questions alongside everything else. Hidden and draft articles are left out. Read-only.
Before you start
- A Document360 API token: in the portal open Settings → Knowledge base portal → API tokens → Generate — READ on articles and categories is enough.
- The token only ever reads; nothing in Document360 is changed.
- Documents → Document360: paste the token into API token.
- If your knowledge base isn't in English, set the language code as Document360 shows it under Settings → Localization & Workspaces (en, de, fr…) under Language in Advanced.
- Choose access groups, Test, then Sync.
What comes in
- Every published article across the project's versions becomes one document headed by its title, with a Category line giving its full path above the body — the article's Markdown when present, its HTML reduced to plain text otherwise — read in the configured language and dated by its last modification.
- Hidden and draft articles are left out entirely. The body is fetched only for articles whose modified stamp moved.
| Language | Optional language code, under Advanced. A project can hold the same article in several languages; articles sync in exactly one. Blank reads English (en). |
|---|
Access
A public help centre stays open to everyone here, matching how it's open on the open internet. A private (or mixed) one instead mirrors its own reader accounts and reader groups automatically, category by category: whoever Document360 grants the project, workspace, version, language or a category becomes a viewer of every article that grant covers, matched by email address and re-checked on every sync. Access granted per article isn't readable here, so an article no mirrored reader reaches falls back to the access groups chosen on the source — as do all private articles when reader accounts can't be read with this token. A workspace that mixes public and private articles is synced wholly under its reader lists, the safe side. Allow-only throughout. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Test reports the project versions the token can see; it fails with a specific reason when Document360 rejects the token or refuses a request. The sync covers the first 20 project versions — a project with more is told so in the sync summary — and 3,000 articles; articles past that cap are held back, not treated as deleted, so what already synced stays searchable. Reader lists are read up to 20,000 reader accounts and 300 reader groups; anything beyond falls back to the source's access groups.
Last updated 20 Sep 2026