Fumadocs on TanStack Start

Toggle organization notification channels and manage optional recipients per preference.

Purpose

Notification Preferences centralize which automated notifications fire for the organization and which users receive each preference. Calls use api.NotificationPreferences for listing, toggling, and recipient CRUD; user pickers draw from api.OrgUsers.list.

Who uses it

Tenant administrators configuring alerting noise and escalation paths.

Prerequisites

Combined guard permissions on /dashboard/configurations include view_notification_preference plus configuration read permissions (view_organization_configuration, view_configuration).
Individual controls wrap CanI — expect buttons to hide without update permissions (update_notification_preference, recipient create/delete codes).

There is no dedicated sidebar entry in the primary navigation tree; open Configurations → Notification Preferences (/dashboard/configurations/notification-preferences). The parent configurations index route is intentionally minimal — use the Notification Preferences tab link rendered at the top of the configurations layout.

Step-by-step

Expand a notification category row.
Toggle Enabled — persists immediately with optimistic UI and toast feedback.
Use Add recipient to search users and attach them to the preference stream.
Remove recipients with the trash action when permitted.

Expected results

Switch positions reflect API state after mutations succeed.
Recipient lists refresh after add/remove operations.

Troubleshooting

Cannot toggle: Confirm update_notification_preference is granted.
User search empty: Broaden search text or verify members exist in the organization.

Notification preferences