Ride Notification Preferences
A user configures which ride notifications they receive. Settings are personal — they only affect the current user.
Who Can Do This
Any authenticated user. Each user manages their own preferences independently.
Overview
Ride notifications are per-ride. Preferences set for one ride do not affect any other ride. Toggles appear in the ride details page under Notifications.
For the full catalog of ride notification events, recipients, and delivery channels, see Notification Reference — Ride Notifications.
Configurable Notifications
The following notification types can be toggled on or off per ride. All default to on.
| Notification | Available to |
|---|---|
| Ride edited | All participants |
| RSVP approved | The RSVP'ing participant |
| RSVP rejected | The RSVP'ing participant |
| New RSVP pending approval | Creator, admins |
| Participant removed | The removed participant |
| Admin role changed | Affected participant |
| Ownership transfer | Creator, target participant |
| Ride deleted | All RSVP'd participants |
| Ride restored | All RSVP'd participants |
| Ride started | Participants who haven't started the ride |
| Invite link rotated | Creator |
System Notifications (Non-Configurable)
Some ride notifications are always delivered regardless of preferences. See Notification Reference — Ride Notifications for the current list.
Rules
- Preferences are scoped to a single ride and do not carry over to other rides.
- When a user performs an action, they do not receive their own action as a notification.
- These preferences are separate from device-level notification settings. A notification is only delivered if both the device setting and the in-app preference permit it.
- Preferences are cleared when a user's RSVP is removed (by themselves or by an admin). If the user is later unblocked and re-RSVPs, their preferences restart at defaults.
Steps
- Open the ride details page.
- Tap Notifications in the ride settings section.
- Toggle each notification type on or off.
- Changes are saved immediately.
Status: partially-live. Backend settings API is complete. Per-ride notification preference toggles in the frontend are not yet built.