> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Manage Notifications

> Configure notification channels and preferences for email, SMS, and push notifications across your PlaneConnection workspace.

This guide explains how to configure notification channels and manage notification preferences for your PlaneConnection workspace.

<Warning>
  This feature requires **administrator** or **workspace owner** permissions. Changes made here
  affect all users in your workspace.
</Warning>

<Info>
  **Who should read this:** Workspace administrators who manage how team members receive
  notifications about safety events, trip updates, and operational alerts.

  **Prerequisites:** Admin or Account Owner role.
</Info>

## Notification channels

PlaneConnection supports three notification channels:

| Channel   | Technology | Description                                                     |
| --------- | ---------- | --------------------------------------------------------------- |
| **Email** | Resend     | Notifications delivered to the user's registered email address. |
| **SMS**   | Twilio     | Text message notifications to the user's mobile number.         |
| **Push**  | VAPID/Web  | Browser push notifications (requires browser permission).       |

## Configure workspace-level settings

Navigate to **Settings > Notifications** (or the relevant section in your workspace settings) to manage default notification behavior.

### Default channel preferences

Set which channels are enabled by default for new users:

| Setting           | Description                                                  |
| ----------------- | ------------------------------------------------------------ |
| **Email enabled** | Email notifications are on by default for all users.         |
| **SMS enabled**   | SMS notifications are on by default (requires phone number). |
| **Push enabled**  | Push notifications are on by default.                        |

### Event categories

Configure which events trigger notifications:

| Category           | Examples                                                              |
| ------------------ | --------------------------------------------------------------------- |
| **Safety**         | New safety report, investigation assigned, CPA due, hazard alert.     |
| **Operations**     | Trip created, trip status change, crew assignment, schedule conflict. |
| **Maintenance**    | Due item approaching, discrepancy reported, MEL deferral expiring.    |
| **Portal**         | New trip request, client message, invoice viewed.                     |
| **Administrative** | New member invitation, role change, security alert.                   |

### Urgency levels

Each event has an urgency level that determines delivery behavior:

| Urgency      | Behavior                                                           |
| ------------ | ------------------------------------------------------------------ |
| **Critical** | Delivered immediately on all enabled channels. Cannot be silenced. |
| **High**     | Delivered immediately on all enabled channels.                     |
| **Normal**   | Delivered per user preferences. May be batched.                    |
| **Low**      | Batched into daily digest emails. Not sent via SMS.                |

## Individual user preferences

Each user can customize their own notification preferences from their profile page. Individual preferences override workspace defaults for non-critical events.

Users can:

* Enable or disable specific channels per event category.
* Set quiet hours during which non-critical notifications are held.
* Choose between immediate delivery and daily digest for normal-urgency events.

<Tip>
  Encourage pilots and crew members to enable SMS notifications for trip assignments and schedule
  changes. Email alone may not reach them in time when they are away from their desk.
</Tip>

## Test notifications

To verify a channel is working:

1. Navigate to your own notification settings.
2. Click **Send Test** next to the channel you want to verify.
3. Confirm you receive the test notification on the expected channel.

## Related

<CardGroup cols={2}>
  <Card title="Notification Channels Reference" href="/en/reference/notification-channels">
    Technical details for all notification channels.
  </Card>

  <Card title="Manage Security" href="/en/how-to/admin/manage-security">
    Security alert notification configuration.
  </Card>

  <Card title="Configure Safety Settings" href="/en/how-to/sms/configure-safety-settings">
    Safety-specific notification triggers.
  </Card>
</CardGroup>