> 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/problems.md). # Problems *** ### What is a problem? A Problem is the cause of one or more potential incidents and can generally be identified because one or more incidents have the same symptoms. In GLPI, The Problem allows you to inform, assign and plan, etc., actions or decisions. Problems are accessible in `Assistance` > `Problems`. *** ### How do I create a problem? A problem object can be created : * from the ticket form * in the Problem tab * or directly from the **`Assistance` > `Problems`** menu. The problem creation form is very similar to the ticket creation form and shares many of the same concepts: Requestor, Observer, Assigned to, Status, Urgency, Impact, Priority, Category. *** ### Can I use the receiver for problems? No, only tickets can be used by the receiver. *** ### Can I customise problem notifications? Yes, in the same way as tickets, Problems notifications can be customised. Go to **`Setup > Notifications > Notification templates`**. --- # 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://help.glpi-project.org/faq/glpi/problems.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.