The Knowledge Base has been rebuilt around a single workspace where you can read and write without switching screens. A modern editor, a navigation tree with favorites, inline comments, version history and built-in translation make documentation easier to create and maintain. Categories give way to nested articles, so you can organize content as you see fit.

Technicians can now keep certain ticket attachments out of the requester's view, and anyone removed from a ticket is notified automatically. Search criteria can be limited per profile, so each team works with the information it actually needs. Project tasks also get reminders, and form questions can now accept several items at once.

Dashboards gain new filters (entity, groups, statuses, SLA, technician, operating system) and new widgets, such as tickets by group and status or computers by age. Pages also load faster, which makes daily monitoring smoother.

When a ticket passes from one team to another, each team now gets its own internal deadline and its own overdue status. Delays are no longer charged to whoever handles the ticket last. Service managers can see exactly where time is lost, and every team is evaluated on what it really controls.

Yes. You don't need to install GLPI 11 first: GLPI 12 contains every database migration since version 0.85.5 and applies them in a single update.

Before you start, make sure your server meets the GLPI 12 requirements. GLPI 10 ran on PHP 7.4+ and MariaDB 10.2+, so most GLPI 10 servers need a PHP and database upgrade first. Then check that each plugin you use has a GLPI 12 compatible version.

Any version from 0.85.5 onwards can be upgraded directly to GLPI 12. Versions older than 0.85.5 must first be brought up to at least 0.85.5. The older the source, the more important a staging test becomes.

PHP 8.3 or later, and MariaDB 10.11+ or MySQL 8.0+. Apache 2, Nginx, lighttpd and IIS are supported as web servers. An official Docker image is also available on Docker Hub.

Official support covers the two latest major versions, so with GLPI 12 released the window moves to GLPI 12 and 11, and GLPI 10 leaves it. Your installation keeps working, but plan your upgrade so you keep receiving security fixes.

Use only plugin versions marked compatible with GLPI 12. For plugin developers, the main changes are: the CSRF token mechanism is replaced by browser-native header validation, the Guzzle and league/csv libraries are no longer bundled, and core classes now use native PHP types. Check our documentation if you have plugins to upgrade.

Yes, in most cases. High-Level API v3 is released alongside v1 and v2, so existing clients keep using the version they target; you opt into v3 with the GLPI-API-Version header or the /api.php/v3.0 endpoint. Webhooks are pinned to a specific API version.

Two things to test on staging: anything that reads Knowledge Base categories, which no longer exist, and webhooks or feeds that target internal addresses.