Every member of your organization can:
There is no permission to grant for this. Out of the box every article is shared with the whole organization, so every member reads everything published. To keep an article or a category to particular people or teams, change its sharing — see Sharing articles and categories.
Everything below is about writing and reviewing, not reading.
| Permission | What it lets you do |
|---|---|
| Create knowledge-base articles | Create articles and edit your own unpublished drafts. |
| Edit knowledge-base articles you authored | Keep editing articles you created after they are published. Requires Create. |
| Edit any member's knowledge-base articles | Edit anyone's articles. An admin override that implies the two above. Also needed to switch on a Spec Reached a Stage automation. |
| Publish knowledge-base articles | Publish, unpublish, and archive articles; edit slugs and audience; switch customer comments on or off; manage and share the category tree; approve or send back proposed changes; move articles into publishers-only stages. Requires Create. |
| Comment on knowledge-base articles | Comment on articles and reply in their review threads; edit and delete your own article comments; resolve threads you started. Requires nothing else. |
| Moderate knowledge-base article comments | Edit, delete, resolve, and reopen any member's article comments. An admin moderation override that implies Comment. |
Holding any of the six gets you into the Manage articles surface and the article editor. Holding none means you read the Library and nothing more. Someone holding only the two comment permissions sees the editor read-only, with the Comments panel active — see Article review comments.
Manage Knowledge Base Settings opens Configure Settings → Knowledge Base, where the workspace's stages are set up. It is a Settings permission: it requires the Settings module, it is not one of the six above, and it does not by itself let you author or open Manage articles.
The default Admin role has it. When it was added, existing admin roles were given it, and so was any role that held Edit any member's knowledge-base articles together with access to Settings. It is not part of any role template.
There are two ways to edit an article you did not write:
Without one of those, the article opens read-only.
Publish knowledge-base articles is the curation permission, not just the publish button. It covers:
A publisher still acts only on articles they can see: an article that is not shared with them is "not found" to them, whatever their permissions.
There are no separate category permissions. If you want someone curating your structure, this is the permission to give them.
| To | You need |
|---|---|
| Add, rename, recolour, reorder or delete stages (Configure Settings → Knowledge Base → Stages) | Manage Knowledge Base Settings |
| Set or clear an article's stage | Create knowledge-base articles plus edit access to the article (your own, a Can edit share, or Edit any member's). Editing a published article's words is not needed |
| Move an article into a publishers-only stage | Publish knowledge-base articles as well |
| Propose a change to a published article under approval | The same as editing its content |
| Submit a proposed change | Being the person who proposed it |
| Withdraw or discard a proposed change | Being the person who proposed it, or Publish knowledge-base articles |
| Approve a proposed change, or request changes | Publish knowledge-base articles |
| Watch an article or category, and see who watches an article | Nothing beyond being able to read it |
| Add or remove other people's watching of an article (Select watchers) | Edit access to the article: Create knowledge-base articles plus your own article, a Can edit share, or Edit any member's |
| Add or remove other people's watching of a category (Manage watchers…) | Publish knowledge-base articles or Edit any member's knowledge-base articles |
The Manage knowledge base template does not include Manage Knowledge Base Settings, so people with only the template can use stages but not set them up. Grant that permission as well to whoever owns your spec process.
| To | You need |
|---|---|
| See a spec's Work items panel, or a work item's Specs section | Any Knowledge Base permission, plus access to the spec. Work items you cannot read, and specs you cannot see, are left out |
| Link a spec to a work item, or remove a link | Create knowledge-base articles, plus access to the spec and permission to read the work item. A link is not an edit, so edit access to the spec is not needed |
| Create work items from a spec (Create work items), and be offered them when you move a spec into a stage that names a work type | Create knowledge-base articles and Create Items And Workstreams, plus the right to add items under the parent you choose |
| Set the work type a stage names | Manage Knowledge Base Settings |
| Record an as-built change on a work item | Edit access to the work item and Create Comment. The note goes into each linked spec only if you could edit that spec by hand; otherwise the spec is marked out of sync |
| Apply or dismiss a waiting as-built note | Create knowledge-base articles, plus edit access to the spec |
| Switch spec checks on or off and choose their model (Configure Settings → Knowledge Base → Specs) | Manage Knowledge Base Settings |
| Accept a spec difference, or mark the spec updated | Edit access to the spec |
| Save a Spec Reached a Stage automation switched on | Edit any member's knowledge-base articles (Manage All Kb Articles on the Permissions page), as well as the automation permissions |
A Spec Reached a Stage automation runs for every spec in the workspace, including drafts and specs not shared with the person who set it up, and can pass their titles to a notification or webhook. That is why saving one switched on needs the permission that can already read every article. People without it do not see the trigger in the automation builder; switching an existing one off is always allowed. See Specs and work items.
DevStride ships a template that bundles the usual authoring set:
Manage knowledge base — Create, edit, publish, and organize knowledge-base articles and categories, and comment on and moderate their review threads.
It grants Create, Edit your own, Publish, Comment, and Moderate. This is the right choice for most people who write documentation.
It deliberately excludes Edit any member's knowledge-base articles. Publish already covers the editorial control you normally need — you can unpublish or archive anything that should not be live — without also handing over the ability to silently rewrite a colleague's words. Grant that one explicitly, per role, when someone genuinely needs it.
| Control | Requires |
|---|---|
| Knowledge Base nav link, Library, article reader | Nothing |
| Manage articles button | Any of the six |
| New Article | Create |
| Title, body, category editing — your own draft | Create |
| Title, body, category editing — your own published article | Edit your own, or Publish |
| Title, body, category editing — someone else's article | Edit any member's, or a Can edit share plus the authoring permission for its state (rows above) |
| Visibility editing | Publish, plus edit rights on that article |
| Publish / Unpublish / Archive / Unarchive | Publish |
| Audience panel — Visibility and Companies | Always shown to editors; changing it needs Publish (visibility also needs edit rights on that article). Without Publish the controls are disabled and a hint says who can change them. |
| Change URL | Publish |
| Configure Settings → Knowledge Base → Stages | Manage Knowledge Base Settings |
| Stage picker in the editor | Create, plus edit rights on that article; a stage marked publishers only also needs Publish |
| Work items panel — reading | Any Knowledge Base permission |
| Link work item, and × to remove a link | Create |
| Create work items, and the Create its work items? prompt after a stage move | Create, plus Create Items And Workstreams |
| No work items filter on Manage articles | Any of the six (anyone who can open Manage articles) |
| Changes to published articles need approval switch on a category | Publish |
| Submit for approval | Being the proposer |
| Withdraw submission / Discard changes | Being the proposer, or Publish |
| Review proposed change (Approve, Request changes) | Publish |
| Watch / Watch category | Nothing beyond reading it |
| Article watcher avatars → Select watchers | Edit rights on that article |
| Category ⋯ → Manage watchers… | Publish, or Edit any member's |
| Category +, ⋯ menu, drag-reordering | Publish |
| Article Sharing panel → Share | Being the article's owner, or Edit any member's |
| Category ⋯ → Share… | Publish, or Edit any member's |
| Comments panel — reading | Any Knowledge Base permission |
| Comments panel — writing (pinning a comment to words included), editing or deleting your own | Comment, plus Can comment on the article. Pinning never needs edit rights |
| Public comment (an answer customers see on the portal) | Comment, plus Can comment on the article, plus the Service Desk permission Send Public Replies |
| Allow customer comments switch | Publish |
| Resolve / Reopen a thread | Comment (threads you started), or Moderate (any thread) |
| Editing or deleting someone else's comment | Moderate |
| Dragging articles to reorder | Publish |
| Filing an article into a category | Edit rights on that article |
| Reading the History panel and previewing a version | Nothing beyond the access that opens the article |
| Restore this version | The same as editing that article's content — see the row above for your case |
| Seeing other members' drafts | Publish, Edit any member's, or Comment — or a Can edit share on that draft |
Archived articles are read-only for everyone regardless of permission. Only Unarchive is offered.
A small team where everyone documents. Give the Manage knowledge base template to everyone who writes. Simple, and the category tree stays tidy because everyone can fix it.
A larger team with editorial control. Give most writers Create plus Edit your own. Give a smaller group Publish as well. Writers draft freely; the publishers decide what goes live, own the structure, and control what customers see. (Create alone is enough for someone who only ever drafts — they can write and file their own drafts, and lose edit access to an article once a publisher takes it live.)
Customer-facing content with a review step. Same as above, and give your reviewers Comment on knowledge-base articles. They can read drafts and leave review comments without being able to change a word. Lean too on the fact that unarchiving always returns an article to draft — retired content can never go live again without someone deliberately republishing it.
They are not per-category. Permissions apply across the whole Knowledge Base. To decide who can read, comment on, or edit one section, share that category instead: giving a team Can edit on Product A lets its writers edit there, alongside their authoring permissions. See Sharing articles and categories.
There is no separate permission for history. Reading an article's history needs only the access that opens the article, and restoring a version needs exactly what editing its content needs — nothing more, nothing less. See Article history and restore.
Customers need no permission to write specs. A signed-in portal customer can write and edit drafts only for their own company, only in a category you opened to client drafts, and only until the draft is published. See Client spec drafts.
A category's audience is not a permission. Marking a category Internal controls who can read it on the customer portal. It has no effect on who can edit it, or on which members see it in the Library — that is the category's sharing.
Article Review Comments
Leave threaded review feedback on a knowledge-base article in its editor, pin a comment to the exact words it is about, mention teammates, and resolve threads once they are dealt with.
Customer Comments on Articles
Let signed-in customers ask questions and comment on an article in the Help center, pinned to the words they mean if they like, and answer them from the article editor with a public comment, which customers in the thread are emailed and can answer by email, or an internal note.