Adding custom fields to GLPI with the Fields plugin
Extending tickets, assets and users with the Fields plugin: containers, field types, required fields, per-profile rights and the migration path from GLPI 10.

Extending GLPI with supported and community plugins: custom fields, purchasing, customer credits, carbon reporting, AI summaries and anonymization.
Extending tickets, assets and users with the Fields plugin: containers, field types, required fields, per-profile rights and the migration path from GLPI 10.
Adding questions to GLPI native forms that technicians see but requesters do not, replacing a FormCreator capability after the move to core forms.
Running purchase orders inside GLPI: product references, approval circuits, budgets, purchase order documents, delivery tracking and automatic asset creation.
Selling prepaid support hours from GLPI: credit types, vouchers per entity, deducting on tasks and solutions, expiry dates and over-consumption rules.
Estimating energy and emissions of computers, monitors and network devices from GLPI inventory, usage profiles and carbon intensity sources.
Setting up the GLPI AI plugin to summarize ticket timelines: OpenAI keys and organization, usage caps, caching and data leaving the instance.
Creating safe test and training copies of GLPI: anonymization profiles for users, entities, computers and email, field-level rules and the fact that changes are permanent.
Marketplace registration keys, manual installs for isolated networks, matching plugin versions to GLPI releases and a separate plugin directory with GLPI_MARKETPLACE_DIR.
Which GLPI plugins need a GLPI Network subscription and at what level, which are free, and how support differs for Teclib-published and community plugins.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.