Knowledge Base

Folders and access

Folders and access

Articles are organised into folders — a browsable tree, like a file system. Folders are also the place where you control who can read which articles.

Folders

Every article has exactly one home folder, chosen as its Category when you write it. Folders can be nested, so you can build a tree such as Servers / Linux / Provisioning. Browse the tree in the Folders section of the Knowledge Base sidebar, below the views (see Browsing the Knowledge Base).

  • Each folder has a colour tile — a small coloured square next to its name. The colour is picked automatically from the folder and stays the same everywhere (the sidebar, the home page cards, the folder’s own page) and for everyone. It is a visual aid only; two folders can share a colour.
  • Each folder shows how many articles it holds — a small count on the right of the folder row. It counts the folder and every subfolder inside it: a folder with 12 articles and two subfolders of 3 articles each shows 18. It counts only the articles you can actually see (published articles, plus your own drafts), so it never reveals more than the folder’s list would, and a subfolder you cannot read adds nothing to its parent’s number. A restricted folder you cannot read shows no number. On an older server the number covers the folder’s own articles only, until the server is updated.
  • A restricted folder shows one padlock on its row — see Restricting a folder. Everyone sees the padlock, not only administrators.
  • Create a top-level folder with the + next to the Folders heading in the sidebar, or with the dashed New folder card on the Knowledge Base home page.
  • Create a sub-folder from the ⋯ menu on the folder you want it inside → New sub-folder here, or with Subfolder on that folder’s page. There is no depth limit — nest as deeply as your documentation needs. The new folder opens as soon as it is created. You can only create a sub-folder inside a folder you can read; the new folder is restricted exactly like its parent.
  • The ⋯ menu appears when you point at a folder row, when you move to it with the keyboard, and always on the selected folder; on a touch screen it is always visible. It holds New sub-folder here, Edit, Move to… (administrators), Access… (administrators) and Delete folder, each shown only to people allowed to use it.
  • Edit a folder from the ⋯ menu → Edit. You can change its name, its description (a sentence shown on its card and on its page) and its order — an optional whole number: lower numbers sort first, and folders without one sort after, by name. Editing never moves the folder or changes who can read it. A description or an order can be changed but not removed yet: if you empty the field, the dialog says so and the current value is kept.
  • Move a folder with Move to… in the same menu. Pick any other folder as the new parent, or Top level (no parent) to pull it back out to the root; the folder’s sub-folders and its articles move with it. Because a move changes who can read everything inside the folder, it needs the manage settings permission (administrators have it), and Move to… only appears for people who hold it. If that permission is taken away while the dialog is open, the move is refused with a message saying so and nothing moves. Each move is recorded in the version history of every article it carries; a move made through a service account (an automation or an AI tool) shows A service account as the author.
  • Names are unique within their parent. Servers / Linux and Workstations / Linux can both exist; two folders named Linux under the same parent cannot. If a name is already taken where you are creating or moving to, the app says so and nothing is changed.
  • A folder cannot be moved inside itself or inside one of its own sub-folders — that would detach the branch from the tree. The move is refused with an explanation.
  • Delete a folder removes it and everything inside it — its sub-folders and all of their articles — from the Knowledge Base. The confirmation tells you exactly how many folders and articles are affected. The articles are soft-deleted (recoverable by an administrator from the database), but this is still a heavy action: read the warning before confirming.

Folders are created, described and ordered here in the Knowledge Base; Settings → Taxonomies sends you here for them.

A folder’s page

Selecting a folder opens its page. At the top, a breadcrumb shows the folder’s full path; each part is a link back up the tree. Below it, a header card holds the folder’s colour tile, name and description, and four facts:

  • Who can see — Everyone with KB access for a public folder. For a restricted one, administrators see the rules in words, such as Only Admins, Only 3 people or Only holders of Finance; everyone else sees Restricted. A folder restricted by a parent says Restricted · from that parent.
  • Articles — the articles filed directly in this folder, without its subfolders. The sidebar number includes the subfolders, so the two differ when a subfolder holds articles.
  • Subfolders — how many folders sit directly inside it.
  • Last change — when an article in the folder was last updated.

The header’s actions:

  • New article here opens the article editor with this folder already chosen as the Category. You can still pick another folder before saving.
  • Subfolder creates a folder inside this one.
  • ⋯ offers Edit, Move to… (administrators), Access… (administrators) and Delete folder — the same menu as in the sidebar.

Under the header, the folder’s sub-folders appear as a row of chips — select one to open it. Then comes In this folder: the folder’s articles, in the same table as the home page but without the Folder column (you are already in it), with the same status filter, sort and filters.

Include subfolders

A folder that has sub-folders shows an Include subfolders switch above its list. Off (the default), the list shows only articles filed directly in the folder. On, it shows the folder’s articles and everything filed anywhere under it, and each article from a sub-folder shows that sub-folder’s name before its summary, so you can still tell where it lives. Last change follows the switch too. Folder access still applies: articles in a sub-folder you cannot read stay out of the list. The switch is part of the page address, so a link you share opens the same way.

To make an article appear in a second folder without moving its home, use an alias — see Linking and discovery. An alias is navigation only and never changes who can read the article.

Access: public by default

A folder with no access rule is Public: every signed-in teammate who can read the Knowledge Base sees its articles. This is the default, so nothing is hidden until you deliberately restrict a folder. Access only ever narrows from public — a folder can never grant more than the Knowledge Base already allows.

Restricting a folder

Restricting access is an administrator action, done per folder from the folder’s ⋯ menu → Access… (in the sidebar or on the folder’s page). You add one or more rules; a person who matches any rule can read the folder (the rules are combined with OR). The rule types are:

  • Users — a named set of specific people.
  • Role — everyone with a given role (Admins, Members or Viewers).
  • App grant — anyone who currently has access to a chosen application. For example, “whoever can use the Finance app may read its runbooks.”
  • Asset assignees — whoever currently holds a chosen asset. For example, “whoever has the on-call laptop sees its break-glass notes.”

The last two are dynamic: they read live access grants and asset assignments at the moment of reading. Revoke someone’s app access or release their asset and their Knowledge Base access disappears automatically — there is no separate Knowledge Base permission to remember to remove when someone leaves a project or the team.

A restricted folder shows a padlock next to its name — in the sidebar, on its home-page card (which also says Restricted), in the article list’s Folder column and in search results. A public folder shows none. A folder that is restricted only because a parent is shows a fainter padlock; point at it to see which parent. Use Make public to remove all rules and return a folder to the default.

Restrictions are inherited downward

A sub-folder is at least as restricted as its parent. If a parent folder is restricted, its children inherit that restriction; an administrator can add a rule on a child to narrow it further, but never to widen it past the parent. A folder that has no rule of its own but sits under a restricted parent shows as Restricted (inherited from …), not Public.

Moving a folder changes what it inherits. Drop a folder under a restricted parent and it — plus everything inside it — becomes at least as restricted as that parent, immediately. Pull it back out to the top level and only its own rule remains. A move never grants access the Knowledge Base did not already allow, but it can widen a folder back to its own rule, so check the destination before moving a folder that was relying on a parent’s restriction.

Moves that change who can read ask first

An article’s home folder is its access rule, so changing the folder changes who can read it. When a move may let more people read something, the app asks before saving:

  • Out of a restricted folder into a public one — changing an article’s Category to a folder that nothing restricts warns that everyone who can read the Knowledge Base will be able to read this article. Moving a folder out from under a restricted parent to a place nothing restricts warns the same about its articles (sub-folders with rules of their own stay restricted by them).
  • Between two differently restricted places — the article, or the moved folder’s articles, will follow the destination’s rules instead. The app cannot tell you who those rules let in, so it says plainly that this may let more people read it.

Cancel leaves everything where it was; confirming saves the move. There is no prompt when the source is public, when the destination keeps every restriction the source had (the same folders, or those plus more — which can only narrow who reads it), or when the folder does not actually change. Moving a document out of a restricted folder is allowed on purpose — drafting a write-up in a restricted folder and publishing it once it is cleaned up is a normal workflow — the prompt is there so it is never done by accident.

[!NOTE] The prompt relies on the server telling the app which folders are restricted. Against a server that predates this, the app cannot tell, so it moves without asking rather than guess.

What restricted means for readers

When a folder is restricted, an article inside it is only readable if all of these hold:

  1. You can read the Knowledge Base at all (the article-read permission).
  2. The article’s home folder is public, or one of its rules matches you, or you are an administrator.
  3. The article is published, or it is your own draft.

If you fail the folder check, the article returns “article not found” — not a “permission denied”. This is deliberate: the server never reveals that a restricted article even exists, the same way it hides other people’s drafts. A document you may not see is simply, to you, not there.

The guarantees behind the lock

A few rules are enforced by the server, not just shown in the interface:

  • Administrators see everything. Folder restrictions scope what non-admins see; they never hide a document from an administrator. (This is visibility within the app — it is unrelated to the Secret Manager, where even an administrator cannot read an encrypted secret value.)
  • The padlock is real, not cosmetic. Access is enforced at the server and database, never by the interface alone. A hidden article cannot be reached by a direct link, a second browser tab, or any other client — the lock holds everywhere, not just on the screen.
  • You can never surface what you cannot see. You cannot alias, share, or otherwise expose an article you are not allowed to read yourself.

See Roles and permissions for how roles and the article-read permission fit together.