Push devices
Push devices
Push devices is where you let MaxSuite send notifications to your browsers, so an approval, an alert or a mention reaches you even when the panel is closed. It lists every browser you have allowed and every other way MaxSuite can reach you. The module is called Browser notifications.
In the sidebar under Admin → Push devices.
This browser
- Three counts across the top: This browser (Allowed, Not allowed or Unsupported), Browsers subscribed, and Ways to reach you, counted across every channel.
- Allow notifications when this browser has not been allowed yet, and Send a test once it has. A browser that does not support notifications, or a page not served over https, says so here.
To get notifications in this browser:
- Open Push devices on the machine and browser you want them on.
- Choose Allow notifications, then allow them when the browser asks.
- Choose Send a test to see one arrive.
Do this on each machine. Notifications keep arriving, even with MaxSuite closed, until you forget the browser here or revoke the permission in the browser. Tapping a notification opens the thing it is about. If the browser refuses, allow notifications for this site in the browser's settings and try again.
Subscribed browsers
Each browser you allowed, one row each, with when you allowed it, when it was Last reached ("never" if not yet) and its status, ok or failing. A laptop and a phone are two rows.
Forget removes one and leaves the others alone. It gets nothing more until somebody allows notifications in that browser again. A browser the push service reports as gone for good is removed by itself the next time a notification fails to reach it.
Every way max can reach you
Each channel, such as Browser, Email and Telegram, with whether it is On, its quiet hours and the kinds of notification you muted. Turn on and Turn off switch a channel for you. Turning a channel off stops MaxSuite using it for you. See Notifications inbox and Notifications and alerts.
Who can do what
| Permission | What it lets you do |
|---|---|
webpush:use — Receive browser notifications | Open Push devices, allow and forget your own browsers, send yourself a test, and turn your channels on and off. |
Everything here is about your own browsers. Nobody can see or change anybody else's. A browser can only be subscribed by a person signed in on it: an API key cannot subscribe one, even a key that acts as you. Notifications are only ever sent to the browsers' own push services.
What happens on its own
Nothing runs on a schedule. Notifications are sent when something happens, through the same rules as every other channel.
Needs
Nothing else switched on.
What agents can do
An agent acting for you can list your browsers, forget one that keeps failing, and send you a test. It works only for a caller with a person behind it: a plain API key is refused. There is no tool to subscribe a browser, so nobody holding a key can point your notifications somewhere else. See Agents and approvals.
webpush.subscriptions(read-only) lists your browsers with when each was last sent to and its last error, if any.webpush.removeSubscription(needs approval) forgets one of your browsers. An id that is not yours removes nothing.webpush.test(needs approval) sends you a test on every subscribed browser and says how many it reached, failed on, or found gone for good (those are removed).
Over MCP the same tools are named webpush__subscriptions and so on.