Portal Notifications
Portal notifications reach people without them opening anything. A leave decision, a reply to a ticket, a new announcement or an approval request arrives on the phone or in the browser as a tray notification, and tapping it opens the item. One portal login can be signed in on several devices and every one of them receives.
How a device is registered
A device registers itself when the person signs in to the portal app or allows notifications in the browser. One row is kept per device, so the same login signed in on a phone and on the web receives on both rather than only on whichever signed in last.
| Event | What happens |
|---|---|
| Sign in | The device is registered, with its platform. |
| Sign out | That one device is unregistered. Other devices keep receiving. |
| A notification is sent | It goes to every registered device of that login. |
| A device stops responding | Its registration is removed automatically when the push service reports the token dead. |
That last point matters: registrations for reinstalled apps and replaced phones are pruned on their own, so the list does not silently fill with devices that will never receive again.
Testing it
The portal app has a self-test that sends a notification to the caller's own devices. It is the quickest way to establish whether a problem is with your setup or with one person's phone — it exercises the whole path, including the tray, tapping through, and arrival while the app is already open.
Use it when somebody says they are not getting notifications. In practice the answer is usually notifications turned off at the operating system level, which the self-test shows immediately.
What sends a notification
| Event | Who is notified |
|---|---|
| An announcement is published | Its audience. |
| A ticket is replied to | The person who raised it. |
| A leave or claim decision | The employee. |
| Something needs approval | The approver. |
| A payment is confirmed or rejected | The customer. |
Push from the ERP side
A push aimed at one user goes to that user. This sounds obvious and is worth stating, because a broadcast where a single recipient was meant is the kind of mistake that is noticed by everybody at once.
If notifications do not arrive
| Check | Why |
|---|---|
| Notifications allowed for the app or site | The commonest cause by a distance. |
| The person is signed in | Signing out unregisters that device deliberately. |
| Run the self-test | Separates your setup from their device. |
| The app has been reinstalled | The old registration is pruned; signing in again registers the new one. |
Notifications are a convenience, not a guarantee of delivery. Anything that must be seen — a payment deadline, a contractual notice — should also exist as something the person will find when they next sign in.