28. 09. 2026
Asset Management, NetEye
30. 09. 2026
Mirko Morandini
Asset Management, GLPI, Knowledge Management, Service Management
GLPI 12: A Practical Review of the Major Changes
New features, remaining gaps to the road-map, and operating-system compatibility.
Starting in 2026, Teclib, the company behind GLPI, is moving from major releases every three to four years to a fixed annual release cycle, with a new major version planned for each October. The aim is to deliver smaller, more frequent changes and make upgrades easier to manage.
GLPI 12 is feature-ready, with general availability scheduled for October 7, 2026. Don’t expect any relevant visible changes on the general asset and ticketing interface. The important changes are quite specific to single functionalities: a completely modernized Knowledge Base, session management and data privacy, sudo mode, group-managed OLAs, accessibility fixes, some dashboard enhancements, and the new API v3.
New features:
A new, modern Knowledge Base
The Knowledge Base was rebuilt from scratch GLPI 12. It has a new interface, a new navigation model and a completely new editor based on Tiptap. The changes affect not just the appearance, but the way users browse, write, review and publish knowledge.
GLPI 12 removes the separate category layer: articles can contain other articles and can be arranged as parent and child content. The Knowledge Base tree is visible in the sidebar, can be expanded and collapsed, and makes related content easy to find. Authors can easily reorganize the tree by dragging an article to a new parent.
- The current article is highlighted in the tree.
- Articles can have an image icon
- Articles can be marked as FAQs or made available in the service catalog.
- Documents, uploads and article information are available from the same workspace.
Writing and review
- New editor: The Tiptap-based editor provides a new rich-text editing experience. Slash commands (press “/”) support fast formatting and embedding of images and video.
- Revisions: the sidebar shows all saved versions, so users can review the article history and open a specific revision.
- Comments: comments are displayed in a side panel with counters and edit and delete actions.
- Permissions: access control is more granular, including separate control over article visibility by scheduled time and by group, profile or entity.
The result is a single Knowledge Base workspace in which readers can navigate an explicit article tree, authors can create and reorganize content, and administrators can manage editing, revisions, comments, permissions, and availability to self-service users in one place.
Session manager and OAuth session revocation
GLPI 12 adds a session manager with authentication-type and date filters. Administrators can list and revoke OAuth client sessions, which makes it possible to remove a specific session after a device loss, role change or integration decommissioning instead of relying on a global logout. Also, each user can view and revoke his active sessions in his personal settings.
Data and privacy
The new “Data and Privacy” tab centralizes GLPI’s data-retention settings. The retention policy for historical logs, previously located under Configuration > General, has been moved here, and several history cleaning options are added. This gives administrators one place to define GDPR-relevant retention options and for keeping the database size small.
Sudo mode for sensitive actions
The Sudo mode introduces an additional confirmation step for privileged operations.
The purpose is to separate routine administration from actions that can change security, permissions or other critical settings. A user may have the required rights but still needs to explicitly confirm the elevated operation. The expected benefits are:
- fewer accidental changes;
- clearer privileged intent;
- better audit-ability;
- less risk from unattended browser sessions.
OLA model and group-managed OLAs
GLPI 12 introduces a new OLA model with group-managed OLAs. Previously, OLAs where like SLAs, with the distinction that SLA timers start always at ticket creation (since it defines the commitment to the requester), while OLA timers (which define internal commitments) started when they were assigned.
Group-managed OLAs better reflect how service desks operate in practice. Tickets can be assigned to different teams during a service request process, and now OLA timers can be tied to single groups, for evaluating the group’s performance.
Security hardening
The GLPI project highlights security hardening in GLPI 12, including work related to SQL and CSRF protection. GLPI 12 should provide stronger protection around database interactions, forged requests, sessions and privileged operations.
Accessibility: concrete changes in GLPI 12
GLPI 12 improves accessibility in the help desk interface, forms, authentication flows and page structure.
- Keyboard operation: forms, drop-downs, selectors and other interactive controls can be operated with the keyboard, including navigation with the Tab key. This also applies to the entity selector.
- Forms and focus: form contrast, keyboard focus and interactive-control behavior are improved. Also the two-factor authentication setup flow is accessible by keyboard and assistive technologies.
- Page structure and assistive technology: pages use descriptive titles, correct h1 headings and clearer landmarks; help desk search fields receive accessible names and auto-complete hints; decorative illustrations and icons are excluded from meaningful output.
Taken together, these changes address relevant RGAA requirements for the GLPI interface. The RGAA (Référentiel général d’amélioration de l’accessibilité) is the French framework for evaluating digital accessibility and is based on Web Content Accessibility Guidelines 2.1 and the European standard EN 301 549. The improvements are therefore also relevant for accessibility assessments and requirements in Europe.
Dashboards and reporting
GLPI 12 adds ticket reports by category/entity, group/status and status. Dashboard filters now cover entities, assigned users, SLA, multiple statuses, operating system and predefined date ranges; a new report shows computer age.
Inventory
The inventory configuration page has been redesigned, including accessibility improvements. Device components can now carry firmware information, network-port metrics can be mapped to computer assets, consumables and cartridges have additional history, and plugs can be linked to assets.
High-Level API v3
The new High-Level API v3 is an extension of v2 that finally adds access to generic objects and generic fields. Permissions can restrict an integration to selected fields rather than the complete object. The API also adds new Knowledge Base fields and several small improvements.
What was yet not implemented in GLPI 12
Several functionalities that are on TecLib’s 2026 road-map are not present in GLPI 12. The hard release date did not permit to include all planned improvements, and 2026 is still not over 😉
- Workflow management: the planned process engine and visual flow editor for advanced automation and workflow management are not part of GLPI 12. This will probably become a plugin that will be available only for higher subscription models.
- Migration of static assets to generic assets: the planned migration of all legacy static assets, except software, into generic assets, was not implemented. It is a huge and time-consuming change that will be shifted to the next major release.
- In line with the previous point, we are still waiting for the predefined assets classes to have the same configuration flexibility as the new generic assets.
Operating-system compatibility
Minimum requirements for GLPI 12 are PHP 8.3 and MariaDB 10.11. For the commonly used Linux distributions we have the following:
- Ubuntu 24.04 LTS and RHEL 10: natively compatible with GLPI 11 and GLPI 12 using the standard packages; no workaround is required.
- RHEL 9: GLPI 11 requires AppStream adjustments, while GLPI 12 is incompatible by default. A GLPI 12 installation needs the REMI repository for PHP 8.3 and an external MariaDB repository. A migration to RHEL 10 or an in-place upgrade to RHEL 10 using the Leapp utility are highly recommended.
- Windows: it will work, if you are an “audacious professional” (cit. a well known GLPI influencer) 😉
Final thoughts
GLPI 12 is not a functional revolution, but a meaningful modernization release. The new Knowledge Base interface and article model are the most visible change, while session management, sudo mode, data and privacy controls, accessibility improvements, and the new API strengthen the platform around them. For administrators, the release adds more control over sessions, privileged actions, data retention and internal service commitments. For users, it improves navigation and accessibility. GLPI 12 is the first step of Teclib’s annual release cycle: a practical upgrade with a clear architecture and manageable scope, while some larger road-map items remain for later releases.
Würth IT Italy, based in Bolzano/Bozen, South Tyrol, is an official GLPI Gold partner for Italy, and for the German speaking market (Germany, Austria, Switzerland) through its spin-off Gravitate.eu.
Mirko Morandini
Mirko Morandini, PhD, is a senior consultant in IT Service Management and Asset Management, with over a decade of experience and numerous successful projects in Germany, Austria and Italy. As the GLPI advocate at Würth IT Italy, Mirko is passionate about open source solutions - and when he’s not optimizing IT processes, he enjoys spending time with his family and playing and conducting wind band music.
Author
Latest posts by Mirko Morandini
31. 03. 2026
Asset Management, GLPI, Service Management
GROUP-based Asset Permissions in GLPI 11: GLPI Rights Management Redefined
29. 09. 2025
Asset Management, GLPI, Knowledge Management, Service Management
Getting the M(u)st out of GLPI
30. 06. 2025
Asset Management, Unified Monitoring
Das neue GLPI 11 – offizielle deutsche Vorstellung [DE]