Enable push notifications and understand live updates

Opt in on a supported device when the platform has enabled Firebase.

When push is available, open Notifications and turn on the Push alerts toggle. Use the sound icon beside it to mute or unmute in-app sounds. You can disable push for this device. Member notifications have no test buttons. On mobile, the notification dropdown spans the screen below the header, with padded sound and push controls. On supported iPhones install Arkilamo on the Home Screen first. Notifications may be delayed or blocked by device settings; use your dashboard for the current status.

Chat, bookings, payment decisions and wallet balances remain controlled by Arkilamo’s server. A push alert is not proof of payment or a confirmed reservation. Open the dashboard to check the latest state.

The initial Firebase rollout adds push foundations and optional live refresh signals. Full offline bookings/chat access, queued offline message delivery and browser live trip tracking are not enabled by this rollout. Existing chat and GPS tools remain available where configured. A suspended or closed browser cannot guarantee continuous GPS tracking.

Administrators can follow five setup steps in API keys & settings → Firebase. Step 1 prepares storage. Step 2 shows the exact Project settings → General → Your apps → Config property for each Web app textbox. Step 3 links to Cloud Messaging for the public VAPID key and Service accounts for the complete private JSON credential. Step 4 provides copyable Firestore rules and the installation-specific cPanel cron command. Step 5 saves and enables Firebase. Delivery monitoring is separate from the settings form, and push tests unlock only after the saved integration is enabled. The optional App Check field can stay blank for the first setup.

Push delivery troubleshooting: FCM accepted means at least one provider send request was accepted; it is not a display receipt. No registered devices means no active device accepted the event, so enable push on each Mac/browser and installed iPhone app, then send a new test. Older Sent rows are labelled Processed (legacy) because their device result was not distinguished. Test device alert / Test this device directly bypasses FCM to request a local OS notification. If it does not appear, check system notification permission and Focus / Do Not Disturb. The updated service worker shows event-specific notifications titled ArkilaMo Update even while Arkilamo is visible and does not require a background session request. After installing the update, use Reload, then turn the Push alerts toggle off and on again on each device.

Push controls use one On/Off toggle for this device. Administrative Firebase monitoring retains diagnostic test icons; these are not shown in member notifications. Icon buttons have accessible labels and hover hints. The toggle turns On only after registration succeeds, and turning it Off is remembered for this account on this browser/device across reloads. Other devices are unaffected. Browser notification permission is still required.

Wallet top-up returns automatically to Wallet after confirmed cancellation or payment. Browser checkout controls belong to the operating system; reopen ArkilaMo if closing checkout does not return automatically. Do not retry payment while reconciliation is pending. Renter affiliates share renter signup links. Attribution stays with the invited account if they choose to host instead. Qualifying live rentals credit one affiliate: renter referrer first, otherwise owner referrer. The affiliate earns commission plus base referral points using the renter earning block and rate, after eligible completion/reconciliation; affiliate points have no repeat bonus and are reversed with refunds. Notification titles use ArkilaMo Update. Push alerts cover booking decisions, named chat replies (including ArkilaMo Care and clearly identified Care AI replies), handover proposals/agreements, confirmed payments and refund review, rental completion, verification decisions and document renewal/expiry, rewards, wallet top-ups/withdrawals/adjustments and affiliate updates. Active bookings receive daily pickup, return or overdue reminders. Built-in staff roles receive relevant submission, report and support-case alerts. Internal document reads and configuration changes do not send member pushes. The Firebase worker must run; recent events have a two-hour recovery window. Queued audit alerts resolve current wording when sent, including entries queued before an update. After installing an update, open the app and use Reload to activate the latest notification worker. New booking requests can say You have a new booking!; booking acceptances are identified, and booking/human-support message alerts can say New message from followed by the sender’s name. Names may appear in lock-screen previews according to device settings; message content and payment balances are not included.