Notifications, push messages and Google Maps settings
What the automatic notification rules send and to whom, what the older Notification Settings and Push Notification pages really do, and how to set the Google Maps key and what happens without it.
Last updated 22 October 2026 · Last verified 22 October 2026
Purpose#
This page covers four places in the delivery-company panel that deal with notifications and maps: the automatic-notification rules in the Notification center, the older Notification Settings page (Firebase secret key and FCM topic), the older Push Notification page for sending a manual message, and the GoogleMap Setting page. The aim is to show which of them do real work and which you can leave alone.
Who can access it#
The three older pages (Notification Settings, Push Notification and GoogleMap Setting) work on the company's own domain only, not on the main platform domain; the Notification center is opened from the company panel menu. Menu items appear only for accounts with the matching permission, and the Setting group itself needs at least one read permission among delivery categories, charges, types, liquid/fragile and packaging.
| Page | Where | What is required |
|---|---|---|
| Notification center («مركز الإشعارات») | Side menu | A company admin or in-charge account that belongs to a company |
| Notification Settings | Setting | notification_settings_read to open, notification_settings_update to save |
| GoogleMap Setting | Setting | The menu link shows for accounts with notification_settings_read |
| Push Notification | Side menu | push_notification_read, push_notification_create, push_notification_delete |
The Push Notification menu item is hidden from company admins and in-charge accounts, because the Notification center replaces it; any account with push_notification_read can still open the page by typing its address.
Automatic notifications: what is sent and to whom#
Open the Notification center and choose the «الإشعارات التلقائية» tab. Each row is one event aimed at one audience (merchants, couriers or company staff), and the channel is a push notification to the person's registered devices. SMS and email are outside these rules (see the guide "Notifications not arriving: push, SMS and email").
- Merchants (on by default): courier assigned for delivery, delivery rescheduled, delivered, partial delivery, returned, wallet top-up requests, withdrawal requests, and store order that did not become a parcel («طلب متجر ما انعمل طرد»). New parcel and Pickup courier assigned are off by default.
- Couriers (on): courier assigned for delivery, pickup courier assigned, and delivery rescheduled.
- Company staff: New parcel and Top-up request from a merchant are on; Delivered and Returned are off by default.
For every row the following applies:
- Each row has an on/off switch, and you can reword the title (up to 150 characters) and the text (up to 500). An empty field means the default text. Variables you can use in the text:
{tracking},{customer},{address},{merchant},{amount},{status}and{reason}. Then press «حفظ» (Save). - A row with the lock icon «موقّف من الإدارة» (stopped by the administration) can be neither switched on nor reworded by the company. The lock shows when the event is off at platform level: either the super admin switched it off, or it is off by default and the super admin has not enabled it yet. So the rows that are off by default (New parcel and Pickup courier assigned for merchants, Delivered and Returned for company staff) stay locked until the super admin enables them. A row that is on at platform level can be switched off or reworded by the company.
- A notification only reaches people who have a registered device. The page shows the warning «الإشعارات مو شغّالة لسا» (notifications are not running yet) when no Firebase service-account file is configured on the server (normally uploaded by the super admin under Firebase settings), and company users are told to contact the administration.
The older Notification Settings page#
It has two required fields: Firebase Secret Key (up to 800 characters) and FCM Topic (up to 20). Spaces are removed from the key, and spaces in the topic become underscores. Only the older sender reads them, and Google has stopped the older interface it relies on; the Notification center does not use these values. So this page does not switch notifications on: ask the super admin to upload the Firebase file instead.
Sending a manual message from Push Notification#
Open the page
Use the Push Notification menu item. The list shows earlier messages with the columns # (row number), image, title, description, user and actions. Press the add (+) button to open the Create Push Notification form.
Fill in the form
Title (required, up to 191 characters), Role (required): All Role or one of the company's roles, User (optional, search by name), File for an optional image, PNG only and up to about 5 MB, and Description (required, up to 1000 characters; formatting tags are stripped when saved).
Save
Press Save. The message is added to the list and sent at once, and the page says "Push Notification successfully added." even if sending failed, because sending errors are only written to the server log and never shown to the user.
Who receives it: with All Role, every user of the company except company admin accounts (type 1); a person you pick counts only if you also pick a specific role. The message goes out three ways: the old Firebase topic (key and topic from Notification Settings), the phone's device token through FCM v1 with a credentials file on the server (not the file uploaded in the Notification center), and browser tokens through the old key. These sends do not appear in the Notification center's log.
Google Maps key#
Open the page
Under Setting choose GoogleMap Setting. In the Arabic interface some of its labels also stay in English («GoogleMap Setting» and «GoogleMap Key») because no Arabic translation exists for them.
Enter the key and save
Paste the key into GoogleMap Key (required, up to 800 characters, spaces removed) and press Save Change. The key is stored for your company only, and the message "Save changed successfully" appears.
Try a map page
Open the hub map page, or the edit form of a courier or a parcel. These pages load the Google Maps library with your company's key: the hub map, the Map Show page of the parcels list (couriers and their parcels), the add and edit forms of couriers, and the parcel edit form for staff and in the merchant panel.
If no key is saved, the platform requests the Google library with an empty key and shows no warning; what the map displays is then decided by Google. The key is written into the page source that the browser receives, so use a key restricted to your site's domain in Google's console.
Common mistakes#
- Filling in Notification Settings and waiting for notifications. The center's rules do not use it.
- Choosing All Role together with one person. The person is ignored and everyone receives the message.
- Choosing a specific role. The sender compares the chosen value with the account-type number (2 merchant, 3 courier and so on), not with the role record, so the audience may not be who you meant. Prefer the Notification center.
- Treating the success message as proof of delivery. It only confirms the save.
Limits and permissions#
- Push reaches only devices registered after the app was opened or browser notifications were allowed.
- The Push Notification list offers add and delete only; saved messages cannot be edited.
- This guide describes the company version of the Notification center; the super admin and a merchant with a private delivery company have a separate version.
- For notifications that do not arrive, see the guide "Notifications not arriving".