Service Catalog in GLPI 11: From Concept to Practice

How to structure and implement a service catalog in GLPI 11 using native forms, with separation between the customer view and the technical view.

A well-structured service catalog transforms ticket opening from a confusing experience into a guided process. See how to implement it in GLPI 11 with native forms.

What it is and why to have a service catalog

The service catalog is the interface between IT and users. Instead of opening a generic ticket describing what is needed, the user chooses the desired service from an organized menu and fills in a specific form.

Benefits:

  • Reduces misclassified tickets
  • Automates assignment and SLA by service type
  • Improves the user experience
  • Generates indicators per service

Structuring the catalog

Step 1: List the services

Group services into clear categories:

  • Access: VPN, email, internal systems, AD
  • Equipment: laptop, monitor, mobile phone, peripherals
  • Network: internet, Wi-Fi, network point
  • Systems: ERP, CRM, BI, database
  • Support: equipment, software, printer issues

Step 2: Define fields per service

Each service needs specific information. Example for "Request VPN access":

  • Justification (required)
  • Access period (start and end)
  • Approving manager (dropdown)

Step 3: Implement in GLPI 11

In GLPI 11, use Assistance > Forms to create each catalog form:

  1. Create the form with the defined fields
  2. Configure the destination ticket category
  3. Set visibility rules by profile (self-service vs. technician)
  4. Configure approvals if necessary

Customer view vs. technical view

The catalog should have two layers:

  • Customer view: simple, with accessible language. The user sees "Request laptop" and fills in a guided form.
  • Technical view: behind the scenes, the ticket is automatically categorized, assigned to the correct group, with SLA and escalation rules applied.

Best practices

  • Start with the 10 most frequently requested services
  • Use names that users understand (avoid technical jargon)
  • Include a description and estimated response time for each service
  • Review the catalog quarterly based on usage data

Next step

With the catalog ready, configure the SLAs per service and implement incident management for tickets that deviate from the standard flow.

Frequently Asked Questions

It is the organized menu of all services that IT offers to users, with a description, SLA, owner and request form. It is the 'storefront' of the Service Desk.

Yes. GLPI 11 incorporated customizable forms into the core, allowing you to create a complete service catalog without external plugins.

In GLPI 10, yes. In GLPI 11, native forms replace FormCreator for most service catalog scenarios.

The user catalog shows services in a simple way (e.g. 'Request VPN access'). The technical catalog details SLAs, metrics, dependencies and approval workflows.

Need help?