> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/profile_settings_and_logout/disable-alarms-for-a-userpage-1.md).
# Disable alarms for a userPage 1
In case a user shall not receive alarms during a certain time e.g. during vacation or absence, the alarms can be disabled in user's profile.
1. Open the profile settings.
2. Enter "From Date" and "To Date" in Disable alarms section.
3. Click "Save" and sign.
4. If you want to enable the alarms then remove "From Date" and "To Date" values and save the new settings.
The system observes the amount of users that will receive the alarms in a given alarm group and warns if there is just one or no one left.
If there is just one user that will receive active alarms from some alarms groups as in the example below:
If this user disables active alarms then all his alarm groups with only him being an active user will have an alarm icon as shown below.
The system will allow to create such a configuration and it is user's responsibility to assure that there is always at least one user that will receive active alarms from the system.
---
# 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.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/profile_settings_and_logout/disable-alarms-for-a-userpage-1.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.
