Enable notifications on Desktop
- Open Settings > Profile.
- Find the Notifications card.
- Select Enable notifications on this device.
- When the browser asks, choose Allow. Crewvana asks only while permission is undecided; it does not repeatedly prompt after a denial.
- Confirm the card shows Push notifications currently enabled and the device appears under Enabled devices.
The setting is specific to the current browser storage context. Another browser, profile, installed app, or device must be enabled separately.
Enable notifications on Mobile
Open the Mobile Settings page and use the Notifications switch. The status can show Checking, On, Off, Not supported, or Blocked in device settings.
On iPhone or iPad, install Crewvana to the Home Screen before enabling push. A normal browser tab may show the Add to Home Screen requirement. An installed app has its own browser storage and does not inherit a subscription from another browser context.
View notification history
Open Notifications to search and review stored notifications, mark one read/unread, or mark all read. Inbox/read state is separate from whether the operating system displayed a push. A notification can exist in Crewvana even when the browser/device did not show it.
Disable or remove a device
- Disable for this device marks the current backend registration disabled.
- Remove deletes the selected saved device row from the profile list.
- Disabling does not remove the browser's underlying PushSubscription, so enabling later can safely reuse it.
Only remove devices you recognize and intend to disconnect.
Troubleshooting
- Not supported: use a browser/device that supports Notifications, service workers, and Push Manager.
- Blocked in device settings/permission denied: Crewvana will not prompt again. Re-enable notifications in browser or device site settings, then return to Profile or Mobile Settings.
- Enable button returns an error: refresh after signing in again if the session expired; confirm the application has a VAPID public key and the service worker can register.
- Permission is allowed but device is missing: use the enable action again. It reuses the existing browser subscription and repairs the backend registration when possible.
- Notification opens the wrong place: preserve its title, time, and destination. Normal notifications fall back to
/notifications; message and call producers provide their own canonical destinations. - No OS banner: check operating-system focus/do-not-disturb settings and provider delivery separately from Crewvana's stored notification history.
Provider and device boundary
Crewvana validates same-origin destinations and maintains one root service worker, but actual provider delivery, an OS-level notification click, and installed iOS/Android behavior require device/provider acceptance testing. A human should perform those tests on an authorized device. This guide did not request notification permission, register a device, or send a real push.