Knowledge base
GLPI knowledge base has two main targets:
Gather internal knowledge for technicians;
Provide information as a public FAQ to enable users to solve simple problems on their own.
Each article of the knowledge base must have one or more targets, being entities, groups, profiles or users, to be readable. As long as an article has no target, it is visible only by its writer, is flagged as unpublished
and appears in table Unpublished articles
on the home page of the knowledge base.
By default, articles are not translatable. However, this functionality can be activated, see general configuration.
It is possible to attach documents to articles of the knowledge base.
Elements which should not be interpreted when displayed can be defined with pre-formated style (<pre>
in HTML). Tags like <VirtualHost>
can therefore be inserted and will be displayed. Other HTML tags (<TAG>...</TAG>
may disappear when editing; to have complete visibility of the text, it is possible to switch to HTML mode where all elements will be visible. The browser may also modify dynamically content (case change, tags adding) when editing.
It is possible to create categories and sub-categories in order to organize browsing (see Configure drop-downs). User can then use several tabs to search and browse knowledge base:
Search This tab is the default tab, displaying recent articles, popular articles and last changes. It allows also to search inside knowledge base.
Knowledge base search tab Browse This tab allows to browse tree structure of categories.
Knowledge base browse tab Manage This tab is only visible for knowledge base administrators. Depending on user's permissions, it is possible to access quickly user's articles, user's unpublished articles, all unpublished articles...
Knowledge base manage tab
The different tabs of an article
Knowledge base
This tab displays a table with article category, subject, content, writer, creation date, last modification date, number of views and FAQ membership.
If an article is unpublished (i.e. has no target), this information will appear in red above number of views.
Target
This tab allows to manage article's targets.
An article is by default personal and therefore only visible by its creator.
For an article to become visible by other users, targets must be added to it, a target being either an entity, a group, a profile or a user who will be able to consult the article.
Edit
This tab allows, if appropriate permission, to modify or delete an article.
Documents
Additional information is stored in the form of external documents which are files uploaded into GLPI. In the Documents tab, documents can be associated and unlinked with the selected item. The management of the documents themselves is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the desired file and optionally the field in which the new document is to be placed. The name of the created document will be based on the name of the added file.

History
The History tab is used to show any changes made to an item. The following information about the changes is available:
ID of the change.
Date and time the change was made.
User who made the change. If this field is not filled, it means that the action was done automatically (For example: automatic inventory update).
Field that was changed.
Description of the change that was made.
The description of the change represents either the difference between the old and the new value (For example with location field: Change HQ to Remote Office A), or the explanation of the action which was carried out (For example: Uninstallation of a software: "Gimp 2.0").
Revision
This tab allows to consult all article revisions: each saved modification of the article will create a revision storing the previous version of the article.
Revisions can be shown and restored.

Comments
This tab allows platform's users to add their comments and discuss the article.

All Information
For an item, all information is displayed on one page from the All tab. This shows all of the tabs of an object's form in one view, one below the other.
Last updated
Was this helpful?