> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/nutzer-fur-eskalationen-konfigurieren.md). # Configure users for escalations ## Overview So that alarms can be escalated to users, the user profiles must have been configured correctly and completely. If you have already created a user, you can subsequently add the necessary information to the user profile. ## Procedure * -[-> Open the user's details](/collection/english-v14/documentation/benutzer/benutzerdaten-anpassen.md) * Fill in the marked fields:


[A]	Email address	Alarms are escalated to this email address.
[B]	Tags	Assign tags to the user. Only if the same tag is assigned to the user as to the escalation can an alarm be escalated to this user. See ->here
[C]	Escalation channels	Specify on which escalation channels the user should be notified. More information can be found under -> Define contact addresses
[D]	Projects	Assign the user to the corresponding project. The user must be assigned to the project in which the escalation is triggered.

--- # 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://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/nutzer-fur-eskalationen-konfigurieren.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.