> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/faq/glpi/support_and_partner.md).

# Support and partner

***

### How to become a partner?

Do you have customers interested in our GLPI Network Cloud (SaaS[^1]) offer?

* Become a partner: [find more information on this page.](https://www.teclib-edition.com/en/partners/become-a-teclib-partner/)
* Or describe your project [on this page](https://portal.glpi-network.com/marketplace/formcreator/front/formdisplay.php?id=15), we will answer you!

***

### Is support included in the offer?

Yes, it is a MOC[^2] support/in-service support package. We fix bugs that you may encounter, we apply security patches, and as planned with you we carry out minor and major updates.

If you wish to benefit from other services (assistance support, advice and assistance with configuration, developments, etc.): this is done under additional estimate/cost (from one of our official partners) after studying your request.

{% hint style="danger" %}
**Warning**

**Cloud services do not include level 1 and level 2**. Only level 3 is included in the offer (correction of bugs impacting the code or impacting services linked to access to your Cloud instance). For assistance with configuration, please refer to the list of our [partners](https://glpi-project.org/partners/)
{% endhint %}

***

### How to contact us?

* If you are already our customer, please, use the **“Support”** function in [your account](https://myaccount.glpi-network.cloud/).
* If you are not a customer yet, please, contact us using [this page.](https://glpi-project.org/contact_us/)

***

### How to get help from a partner?

You can discover how GLPI works and configure it yourself, then contact an official partner-integrator if you encounter difficulties or if you want to speed up the configuration of your instance by being accompanied by a professional.

Consult our partners on this [page](https://glpi-project.org/partners/)

***

### What is a patch?

A file **patch** is a set of changes (+/-) designed to update, fix, improve or remove lines in GLPI source code.

Here is an example of **bug-fix.diff**

![Alt text](/files/mqPzAVR2J8Uxz9mGLMII)

* The **+** informs that we add some code
* The **-** informs that we remove some code

***

### How to apply a patch?

A [procedure](/tutorials/procedures/appliquer_un_patch.md) is available to help you apply your patch

***

### What plugins are supported?

You can find the list of supported plugins on [this page](broken://spaces/T0zn1QaI43c7I5x8k4gL)

[^1]: Software As A Service

[^2]: Maintenance in Operational Condition


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/faq/glpi/support_and_partner.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.