The knowledge base gathers answers written once and for all: internal procedures for employees, public help for external people. It avoids requests (articles are suggested while filing) and helps agents reply. This article explains how to write, publish and maintain articles, and how readers use them.
Before you start #
- To write, you need the Knowledge base writer right: Access to read articles being written, Execute to write, publish, archive and classify. It applies to all services.
- A service manager without this right reviews, publishes or archives the articles attached to their service, without creating or editing them.
- To read the internal help, the right to file requests is enough (granted to all employees by default), as is being an agent or a writer.
The article list #
Open Help desk › Knowledge base. Filter by status (Drafts, Published, Archived, To review), category or service, and search titles. For each article: who can read it, its status, its reads, the date it was edited and the “helpful / not helpful” votes.

Write and publish an article #
- Click New article.
- In Article languages, write the Title and the text in each useful language (French, English, German, Italian). The editor handles headings, bold, italic, lists, quotes, links and images.
- Choose the Fallback language, read by whoever reads a language the article does not have.
- Set Who can read it: Employees, External (portal) or Employees and external.
- File the article in a Category, optionally attach it to a Service (its manager can then review and publish it) and add Keywords that help the search.
- Set a Review date if needed: on that day, the last writer gets a reminder.
- Click Save (draft), then Publish. View as a reader shows the result.

Editing, versions and archiving #
- Editing a published article creates Unpublished changes: readers see the published version until Publish the changes.
- Published versions keeps the history; Go back to the previous version publishes it again.
- Archive takes the article out of reading; links already sent lead to a neutral message. An archived article can be published again.
- A draft that was never published can be deleted.
Categories #
Categories have two levels: a category, then its sub-categories. Writers create, rename and delete them from the knowledge base, with the Categories button. A category in use cannot be deleted.
Create an article from a ticket #
On a resolved or closed ticket, a writer clicks Create an article: a draft takes up the reply, without the requester’s name or attachments. They review it before publishing. A draft can also be created from a problem’s solution (see Major incidents and problems).
What readers see #
Employees open Help desk › Help: search, categories and most-read articles. At the bottom, Make a request leads to filing a request. External people read the “External” articles on the external portal.

- While filing, articles that seem to answer the question are suggested; “My problem is solved” drops the request and counts a request avoided.
- Under each article: Did this article help you? Yes or No, and an optional comment. Votes and comments are anonymous.
- Writers read this feedback in Reader feedback on the article page: reads, votes, requests avoided, comments.
- Agents insert a link to an article in their replies (Insert an article): an employee is taken to the Help page, an external person to the portal.
Good to know #
- An archived article is no longer suggested or readable; a link already sent shows “This article is no longer available”.
- Internal articles are never visible on the external portal, not even by direct link.
- The review reminder is sent once per date; a new date opens a new one.
