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

# Notification Preferences

> Control which notification types you receive and through which channels: in-app, email, SMS, and push.

All authenticated users can manage their notification preferences at `/notifications/preferences`. This route renders `NotificationPreferencesPage` from `src/platform/notifications/NotificationPreferencesPage.tsx` with no additional permission gate.

## Overview

The Notification Preferences page allows users to toggle notification delivery by type and channel. Notification types span four categories: `forms` (submitted, approved, rejected), `automation` (failed, succeeded), `tasks` (assigned, due, overdue, completed), and `system` categories. Channels include `in_app`, `email`, `sms`, and `push`. Preferences are persisted via `useNotificationPreferences()`. The push channel is configured through `PushNotificationSettings`. The page is organized with tabs for each category and per-channel toggles. A link to `/notifications/test` is available for testing delivery.

## Who it's for

Access follows your organization's role and module configuration. Any authenticated user may adjust their own preferences.

## Before you start

* You must be signed in.

## Steps

1. Navigate to `/notifications/preferences` or select **Notifications > Preferences** in the navigation.
2. Select a category tab (Forms, Automation, Tasks, System).
3. Toggle each notification type on or off for the channels you want.
4. Changes are saved automatically or on explicit save depending on the implementation.

## Key concepts

**Channels** — `in_app` delivers banners within the platform; `email` sends to your registered address; `sms` sends a text message; `push` sends a browser or mobile push notification.

**Notification types** — Each type maps to a database enum `notification_type`. The list includes `form_submitted`, `form_approved`, `form_rejected`, `automation_failed`, `automation_succeeded`, `task_assigned`, and others.

## Related

<Columns cols={2}>
  <Card title="Platform Foundation" icon="layer-group" href="/pf/overview">
    Platform Foundation overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/platform.tsx
  * src/platform/notifications/NotificationPreferencesPage.tsx
  * src/platform/notifications/useNotificationPreferences.ts
</Accordion>