# Get Notifications

MaaS can notify you when alerts trigger on your system. Your account comes pre-configured with a default notification rule that covers all severity levels — you just need to set up your preferred notification channels.

***

## Where to Find Notification Settings

Look for the **Notifications** submenu item in the bottom left of the interface, under your user profile.

<figure><img src="https://1030294288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvb3mSIMfASX8vMnbtyli%2Fuploads%2Fgit-blob-4ec179899e8aa0a5d94e07236d269c1070b18eae%2Fnotifications-menu-location.png?alt=media" alt=""><figcaption><p>Notifications menu location in the bottom left</p></figcaption></figure>

***

## Setting Your Timezone

{% hint style="warning" %}
Before configuring notification schedules, **set your timezone** in your Profile settings — located directly above the Notifications menu item. If your timezone is wrong, your "When Active" schedules will trigger at the wrong times.
{% endhint %}

***

## Notification Channels

Your account comes with several pre-configured notification channels. Each one is disabled by default — enable and configure the ones you want to use.

<figure><img src="https://1030294288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvb3mSIMfASX8vMnbtyli%2Fuploads%2Fgit-blob-18b429db547198aa3300a6d2314ac9b259685ab9%2Fnotifications-example-list.png?alt=media" alt=""><figcaption><p>Example notification list showing configured channels</p></figcaption></figure>

### Email

<figure><img src="https://1030294288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvb3mSIMfASX8vMnbtyli%2Fuploads%2Fgit-blob-b73fd87c6d3eac00fe29a6b66135069b24bbe8ca%2Fnotifications-email-edit.png?alt=media" alt=""><figcaption><p>Email notification channel configuration</p></figcaption></figure>

| Channel                     | Description                                                                  |
| --------------------------- | ---------------------------------------------------------------------------- |
| **Email: DNR TB**           | Notifications from <donotreply@telcobridges.com>. Enter your email address.  |
| **Email: DNR TB Secondary** | Identical to the primary — use it to configure different notification hours. |

{% hint style="warning" %}
Your email channel is also used for password recovery. You can leave it disabled if you don't want email notifications, but **do not delete it** — without it, password resets require contacting **<support@telcobridges.com>**.
{% endhint %}

### PagerDuty

| Channel                 | Description                                                                  |
| ----------------------- | ---------------------------------------------------------------------------- |
| **PagerDuty**           | Send alerts to your PagerDuty service. Enter your Integration Key.           |
| **PagerDuty Secondary** | Identical to the primary — use it to configure different notification hours. |

To find your Integration Key: open your PagerDuty service, go to the **Integrations** tab, and copy the 32-character Integration Key. See the [PagerDuty integration documentation](https://support.pagerduty.com/main/docs/services-and-integrations) for details.

### Slack

| Channel         | Description                                                |
| --------------- | ---------------------------------------------------------- |
| **Slack: BYOB** | Bring Your Own Bot — connect MaaS to your Slack workspace. |

**Send To format:** `C0123456789|xoxb-your-token`

The first part is your Slack channel or user ID, followed by a pipe (`|`), followed by your bot token.

{% stepper %}
{% step %}

#### Create a Slack App

Go to [Your Apps](https://api.slack.com/apps), click **Create an App**, select **From scratch**, and specify a name and your workspace. See the [Slack app setup guide](https://docs.slack.dev/app-management/quickstart-app-settings/) for full details.
{% endstep %}

{% step %}

#### Add Bot Scopes

In the **Add features and functionality** section, select **Bots** and click **Review Scopes to Add**. Under **Bot Token Scopes**, add the following OAuth scopes:

* `chat:write`
* `im:write`
* `groups:write`
* `reactions:write`
  {% endstep %}

{% step %}

#### Install and Get Token

In **Settings > Install App**, click **Install to Workspace**, then **Allow**. Copy the **Bot User OAuth Access Token** (starts with `xoxb-`).
{% endstep %}

{% step %}

#### Get Your Channel or User ID

Find the channel or user ID you want notifications sent to. In Slack, right-click a channel name and select **View channel details** — the ID is at the bottom of the popup.
{% endstep %}

{% step %}

#### Enter in MaaS

Combine them in the Send To field: `C0123456789|xoxb-your-token-here`
{% endstep %}
{% endstepper %}

### Telegram

| Channel                       | Description                                 |
| ----------------------------- | ------------------------------------------- |
| **Telegram: TelcoBridgesBot** | Receive notifications via our Telegram bot. |

**Setup:**

1. Open our bot: <https://t.me/TelcoBridgesBot>
2. Send the bot `/start` to give it permission to message you
3. Find your Telegram user ID or channel ID — use [@myidbot](https://t.me/myidbot) (send it `/getid`)
4. Enter your ID in the **Send To** field

***

## When Active (Notification Schedule)

Each notification channel has a **When Active** field that controls when you receive notifications. The default is `1-7,00:00-24:00` (24/7).

The format uses day numbers (1 = Monday, 7 = Sunday) and 24-hour time ranges:

```
d-d,hh:mm-hh:mm
```

**Common examples:**

| Schedule                             | Format                            |
| ------------------------------------ | --------------------------------- |
| 24/7 (default)                       | `1-7,00:00-24:00`                 |
| Business hours (Mon–Fri, 9am–6pm)    | `1-5,09:00-18:00`                 |
| Business hours + weekend daytime     | `1-5,09:00-18:00;6-7,10:00-16:00` |
| Weekdays only, all day               | `1-5,00:00-24:00`                 |
| Overnight on-call (Mon–Fri, 6pm–9am) | `1-5,18:00-24:00;2-6,00:00-09:00` |
| Weekends only                        | `6-7,00:00-24:00`                 |

{% hint style="info" %}
This is why there are **two channels** for Email and PagerDuty — you can set different schedules on each. For example, send to your work email during business hours and your personal email after hours.
{% endhint %}

***

## Choosing Severity Levels

Your notification settings include a severity filter. The available levels are:

| Severity    | What It Covers                                                         |
| ----------- | ---------------------------------------------------------------------- |
| Disaster    | Complete monitoring loss (no data received)                            |
| High        | Host down, NAP registration failure, critical CPU/RAM/disk, port down  |
| Average     | Elevated CPU/disk, line bouncing, firewall alerts, scheduling problems |
| Warning     | NAP down, NAP congestion, license warnings, config backup failures     |
| Information | Reboot required, config changes, backup confirmations                  |

**Our recommendation:** Enable **Average, High, and Disaster** for most users.

{% hint style="info" %}
If you enable **Information**, be aware you will receive a nightly notification confirming that the configuration backup completed successfully.
{% endhint %}

{% hint style="warning" %}
Enabling **Warning** can generate noise if you have NAPs or trunks that flap frequently.
{% endhint %}

***

## Custom Notification Rules

The default notification rule is managed by TelcoBridges and covers all alerts for all users. If you need custom behavior — such as muting a specific NAP, suppressing a particular alert, or adding a delay before notification (e.g., "don't notify until it's been down for 5 minutes") — contact **<support@telcobridges.com>**.