Notifications: the bell, e-mail and mobile devices

Purpose#

The platform tells people about things through three channels: the bell in the web panel (in-app), e-mail, and push messages to the mobile apps. This guide explains the bell and its read state, which events send e-mail, and how mobile devices are registered. Push delivery problems are covered in the notification troubleshooting guide.

The bell (in-app notifications)#

The bell icon sits in the top bar of the super admin, company staff and merchant panels. Couriers have no web panel, so no bell. It lists entries from the last 14 days (or since the platform's notifications start date, if that is more recent):

Each entry shows its label, subject, "From: name" and the time. The badge counts unread entries and shows "9+" above nine; the menu shows the 8 newest. Parcel, wallet and store events do not appear in the bell.

1. Open the bell

   Press the bell. Unread entries are highlighted; with none, it says "No new notifications".

2. Open an entry

   Pressing an entry marks it read and opens the ticket, or the news and offers page.

3. Mark all as read

   Press Mark all as read. It marks every listed entry as read for you only; other users are not affected.

E-mail notifications#

E-mail is sent only if the platform administrator has set up outgoing mail.

Parcel status, wallet and store events send no e-mail. A merchant's sign-up code arrives by SMS, not e-mail, and the code-based sign-up (on the web or in the merchant app) sends no welcome e-mail.

Mobile devices#

• Registration. A signed-in app registers a device by calling POST /api/v10/fcm-subscribe with the device token (required; the platform is optional: android, ios or web), and this works even when the plan subscription has expired. The server stores the device and subscribes it to its notification topics: all, role, company, and company plus role. A device that moves to another user or company is unsubscribed from its old topics. POST /api/v10/fcm-unsubscribe removes a device registration. The server code does not show whether a given app version calls these endpoints automatically after sign-in.

Common mistakes#

• Expecting a bell entry for a parcel event. Those go to push only, if the device is registered.
• Company registration fails with "Something went wrong." If the e-mail with the code cannot be sent (for example because outgoing mail is not set up correctly), the registration is rolled back and this message is shown; other errors during sign-up show the same message. Ask the platform administrator to check the outgoing mail setup.
• No push on a device. A device receives topic pushes only after it has been registered with the server (see Registration above).

Limits and permissions#

• The bell is per user; read state is not shared.
• Device registration needs a signed-in user and a device token.