---
description: "How to configure notifications at instance level (administrator): mandatory channels and types, bot and scenario"
---

# How to configure notifications for the instance (administrator)

This guide is for an administrator or any user with rights to **operator panel settings**: here you set **mandatory** channels and notification types for all operators and connect a **bot with a scenario** for delivery via messengers (Telegram, Viber, and so on).

Personal choices (which events and channels each operator uses) remain under **Profile → Notifications** — see the [Notification Center reference](../operator-hub.md).

## When it is useful

- Certain channels (for example, banner or sound) must not be possible to turn off in profiles.
- Certain **notification types** must always stay on for everyone.
- You need bot-based delivery: pick a bot, a scenario section, and entry points for “login” and for sending notifications.
- You can mark **SLA** and **normative response** types as mandatory so operators cannot turn them off — useful when the whole team must receive SLA or response-time alerts. Operators still choose delivery channels unless those channels are also mandatory.

## What to know

- The **Notification settings** page in **Settings** is usually available when the **Notification Center** is enabled on the instance — your platform administrator controls that.
- How **root** enables the Notification Center (instance feature flags) and what changes afterwards: [How to enable the Notification Center on the instance](./enable-notification-center.md).
- **Bell notifications** stay on by default; they cannot be disabled as a mandatory channel.
- **Bot channel** delivery requires a bot with **connected** messenger channels. Some channels are **not supported** in this mode (for example, Facebook Messenger, Instagram, widget) — the UI explains why they are not listed.
- After you configure the instance, operators still **authorize** external channels in their profile (for example, **Log in with Telegram**) when required for delivery.

## Before you start

- [x] You are logged in with access to operator panel **Settings** (including saving changes in that section).
- [x] For the bot tab: you have a bot with the required channels connected; in the scenario builder you prepared a **section** with entry-point nodes for user authorization and for sending notifications (typical aliases in the UI hints are like `notifications-login` and `notifications-entry`).

## Step-by-step

### 1. Open notification settings

1. Go to **Settings** (`/settings-page`).
2. In the sidebar, open the **Settings** subgroup (operator panel settings).
3. Click **Notification settings** (`/settings-page/op-settings/notifications`).

### 2. Tab “Mandatory channels”

1. Select channels that operators **cannot turn off** in their profile — for example, banner, sound, email, Telegram, browser notifications, bot channel — according to your policy.
2. Save with **Save** at the top of the operator panel settings screen (same as other `op-settings` pages).

### 3. Tab “Mandatory notification types”

1. Select event types that must stay **always enabled** for users (they cannot be disabled in the profile).
2. Read any notices: some types may be temporarily unavailable for mandatory enforcement until the functionality is connected on the instance.
3. Save with the same **Save** button in the header.

### 4. Tab “Channel configuration” (bot and scenario)

1. Under **Notifications via bot**, select a **bot**.
2. Select a scenario **section** that contains your entry-point nodes. If there is no section yet, you can **create** one using the button in the interface (clearing the section field may reveal the action — follow on-screen hints).
3. For the selected section, specify:
   - **Login entry point** — node used for first authorization in the messenger (linking the profile to the channel).
   - **Notifications entry point** — node the system calls to **send** messages to the user.
4. Under **Enabled channels**, select messengers allowed for notification delivery (only channels already connected to this bot appear). If the list is empty, connect channels to the bot in bot settings first.
5. Save with **Save** at the top.

Operators can then enable the corresponding channels under **Profile → Notifications** and complete linking if needed.

## Result

- Instance policy for mandatory channels and types is set.
- Messenger delivery is wired to a bot and scenario (section and entry points).

## Related materials

- [How to enable the Notification Center on the instance (root)](./enable-notification-center.md)
- [Notification Center — operator reference](../operator-hub.md)
- [How to configure a notification for an event type (operator)](configure-notification-type.md)
- [Configure system settings](../../settings/how-to/configure-system-settings.md)