# Configuring notifications

System event notifications are used to alert RAS administrators about system events via email. You can configure system event notifications in **Farm** > **Site** > **Settings** > **Notifications**. For the complete description of this functionality, please see [**System event notifications**](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/common-management-tasks/system-event-notifications). The rest of this section describes notifications, which are specifics to Tenant Broker and Tenants.

## **Tenant event notifications**

As a Tenant Broker administrator, you can receive notifications about the following Tenant events:

* **New Tenant enrollment**. Triggers when a new Tenant joins the Tenant Broker.
* **Tenant unjoins the broker**. Triggers when a registered Tenant unjoins the Tenant Broker.
* **Tenant status alert**. Triggers when the RAS Connection Broker in a Tenant Farm goes offline.

When a Tenant event occurs, the Tenant Broker administrator receives an email containing the following information (depending on the event type):

* Tenant name.
* Tenant Broker name.
* Tenant enrollment method (invitation hash or secret key).
* Tenant status.
* Date.

To enable Tenant notifications, do the following:

1. Log in to the Tenant Broker.
2. In the RAS Console, navigate to **Farm** > **Site** > **Settings** > **Notifications**.
3. In the **Notification handlers** section, click **Tasks** > **New** > **Tenant events**.
4. In the **Tenant Events Notification Handler Properties** dialog, specify the following:
   * On the **General** tab, select the **Send email to RAS administrators** option and specify one or more email addresses separated by a semicolon.
   * On the **Settings** tab, either select the **Use the default settings** option (to use Site defaults) or clear it and specify your own settings.
5. Click **OK** to save your settings and close the dialog.

## **Tenant Broker event notifications**

A Tenant Farm administrator can receive notifications when the Tenant Broker becomes unavailable. This usually happens when the RAS Connection Broker in the Tenant Broker goes offline. The notification handler is configured the same way as described above, but this one is configured in the Tenant Farm (not the Tenant Broker).

## **Common event notifications**

In addition to the **Tenant events** handler, you can configure notifications for common events, such CPU utilization, Memory utilization, RAS Agent events, etc. The only limitation here when it comes to Tenant Broker is the Tenant Broker has a limited set of system events for which notification handlers can be configured (see the list of available handlers below). This is due to the fact that the Tenant Broker doesn't have RD Sessions Hosts, Provider, licensing limits, published resources, etc. A Tenant Farm has the complete set of notification handlers, so the Tenant admin can configure any of them.

The following notification handlers are available in the Tenant Broker:

* CPU utilization
* Memory utilization
* Number of gateway tunneled sessions
* Failed gateway tunneled sessions
* RAS Agent events

For additional information, please see [**System event notifications**](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/common-management-tasks/system-event-notifications).


---

# Agent Instructions: 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:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/configuring-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.