The Knowledge Base is a stand-alone application that hosts every help article published by the company. The same content surfaces in three different views — pick the one matching what you're trying to do.
The three views
Public reader at https://mydoc24.org/ — the main browser view, with a hub page, folder pages, and per-article pages. This is what readers land on when they follow a public link.
Admin at /admin — where authors create, edit, publish, and archive content. Only signed-in authors with the right roles reach it. It is opened from the user menu in the site header (top-right), where it appears as Articles & folders.
Chat-widget Help tab inside mywork — a compact reader embedded in the floating chat-widget. Same articles, smaller surface, no top navigation.
The public reader
The hub at / has a search bar in the header area, then a Folders grid: every top-level folder as a card with a recursive count of published articles. Below the folder grid is the list of root articles — published articles that aren't filed under any folder.
Click a folder card to open /f/. That page has a hero banner with a breadcrumb, the folder name, a total article count (including subfolders), the same search bar, then a Subfolders grid and the folder's articles. Click an article title to open /a/.
Each article view has:
A breadcrumb at the top showing the folder path.
The article body, rendered as sanitised HTML.
A sticky On this page sidebar at desktop widths, jumping to each H1/H2/H3 inside the body.
A Related articles card grid below the body, auto-derived from the article's keywords plus its heading text. The Related panel is scoped to the article's content cluster — it never pulls in articles from a different top-level folder, so an article under the Knowledge Base folder will never suggest articles from a Daily usage folder and vice versa. Root articles (no folder) only relate to other root articles.
The admin landing
/admin is titled Articles & folders. It shows an Uncategorised block (articles with no folder) followed by a single Folder tree section, where each folder row is followed by its article rows and its subfolders, indented. Rows are clean div-rows with an icon on the left, name and slug in the middle, and a status badge plus actions on the right. The full set of operations is documented in Manage articles and folders.
Above the tree, a Show row offers three chips — All, Draft, Published — that filter the article rows. Folders stay visible in every mode so the structure never collapses.
The New article button at the top-right of the page opens /admin/new for a fresh draft. The + New folder disclosure at the bottom of the Folder tree section expands inline; type a name, optionally pick a parent, and click Create.
Every article row has Edit and, for published articles, View. Draft rows have a Delete action instead of View — it permanently removes the draft after a confirmation prompt. Folder rows have Rename, Move, and Delete as inline actions that swap the row into edit mode without leaving the page.
The header also offers Public view (back to /) and, for users who can manage groups, Permission rules.
The chat-widget Help tab
mywork's floating chat-widget has tabs at the bottom: Chats, Notifications, Calls, and Help. The Help tab renders the Knowledge Base inside a Shadow-DOM-isolated Web Component so the host page's CSS can't bleed into the widget — and the widget's CSS can't bleed out. It talks to mywork's own server-side proxy rather than to the Knowledge Base directly, and it opens with a Suggested for this page block when the current mywork screen has matching articles. See The chat-widget Help tab for the full tour, including the click-interception that lets internal /a/ links re-render inside the widget instead of opening a new tab.
Where each role lives
Authors spend time in The Editor at /admin/edit/ and in Manage articles and folders at /admin.
Readers stay in the public reader or the chat-widget. They shouldn't see admin URLs and don't need to.
Agents (Claude / scripts) call the import API directly without touching either the admin or the editor — see the agent API docs.
Storage
Articles, folders, and uploaded blobs live in the kb-app's MySQL database (a separate database on the same MySQL server as mywork). Each article has a status — see Article statuses field definitions for what each one means and where it shows up.
Where to next
The Editor — what authors use to write articles.
Manage articles and folders — admin landing workflows in detail.
Article statuses field definitions — DRAFT / PUBLISHED / ARCHIVED reference.
Search the Knowledge Base — how search ranks and what it indexes.
Insert images and embeds — adding media to articles.
Editor keyboard shortcuts field definitions — every shortcut at a glance.