> 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/documentation/modules/configuration/notifications/alarm_options.md). # Alarm options At the entity level, you can configure the alarm options (cartridge/consumable stock alarms, expiration alarms, etc). By default, these options will inherit the value from their parent entity. * Cartridges > Reminders frequency for alarms on cartridges * Cartridges > Default threshold for cartridges count * Consumables > Reminders frequency for alarms on consumables * Consumables > Default threshold for consumables count * Contract > Alarms on contracts - Contract > Default value * Contract > Send contract alarms before * Financial and administrative information > Alarms on financial and administrative information * Financial and administrative information > Default value * Financial and administrative inform ation > Send financial and administrative information alarms before * Licenses > Alarms on expired licenses * Licenses > Send license alarms before * Certificates > Alarms on expired certificates * Certificates > Send certificates alarms before * Reservations > Alerts on reservations * Tickets > Alerts on tickets which are not solved since * Domains > Alarms on domains expiries * Domains > Domains closes expiries * Domains > Domains expired --- # 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/documentation/modules/configuration/notifications/alarm_options.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.