> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/integrations/glpi.md). # GLPI The GLPI integration connects Boza to your GLPI IT asset management instance. It imports your GLPI users to track access and licenses, and can create or remove GLPI accounts automatically as part of onboarding and offboarding.
GLPI integration panel in Boza with the authorize step
## What Boza Does with GLPI * **User sync** — imports the users registered in GLPI (by email) so Boza can track who has access and reconcile licenses. * **Account provisioning** — when GLPI is included in an [Onboarding or Offboarding](/docs/user-management/onboarding-offboarding.md) workflow, Boza can create a new GLPI user as someone joins, or delete their account when they leave. ## What Data Is Synced | Data Type | Purpose | | ---------------------- | ----------------------------------- | | GLPI users (email, ID) | Track access and reconcile licenses | ## Setup GLPI is connected with an API token rather than OAuth, so you'll first generate a token inside GLPI. ### 1. Create an API token in GLPI 1. In GLPI, make sure the **REST API** is enabled (under **Setup > General > API**). 2. Generate an **API token** for a user account that has permission to search — and, if you plan to use provisioning, create and delete — users. ### 2. Connect in Boza 1. Open **Integrations** from the main navigation. 2. Select **GLPI** and click **Connect**. 3. Enter your credentials: * **Instance URL** — your GLPI base URL (the address that serves the GLPI API). * **API Token** — the token you generated above. 4. Click **Submit Credentials**. Synchronization starts automatically and refreshes daily. ## Prerequisites * A GLPI instance with the REST API enabled. * An API token for an account with permission to search users (and to create/delete users if you use provisioning). * Administrator permissions in Boza. ## Need Help? If you have questions or run into issues, contact us at ****. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://boza.gitbook.io/docs/integrations/glpi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.