> 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/platform/platform-core/alert-and-escalation/escalations/configure-users-for-escalations.md).

# Configure Users for Escalations

## Overview

For alarms to be escalated to users, the user profiles must have been configured correctly and completely.

If you have already created a user, you can add the necessary information to the user profile afterward.

## Procedure

* [-> Open the user data of the user](/collection/mandatory-base/platform-core/workspace-and-identity/users/customize-user-data.md)
* Fill in the marked fields:

<figure><img src="/files/TzHQPPCggqsZILguig7K" alt=""><figcaption><p>Fig. 1 – Information of a user profile</p></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="74.33333333333331"></th><th width="182"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Email address</td><td>Alarms are escalated to this email address.</td></tr><tr><td><strong>[B]</strong></td><td>Tags</td><td><p>Assign tags to the user.</p><p>Only if the user is assigned the same tag as the escalation can an alarm be escalated to this user. See <a href="/pages/AmZ0unfBCC8yon0W2prQ">->here</a></p></td></tr><tr><td><strong>[C]</strong></td><td>Escalation channels</td><td>Specify on which escalation channels the user should be notified. You can find more information under <a href="/pages/4xjqjX7NHdvRLOPcTr09">-> Set contact addresses</a></td></tr><tr><td><strong>[D]</strong></td><td>Tenants</td><td><p>Assign the user to the corresponding tenant.</p><p>The user must be assigned to the tenant in which the escalation is triggered.</p></td></tr></tbody></table>


---

# 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://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/configure-users-for-escalations.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.