On your phone instead of an inbox
Requests rarely sit unanswered out of unwillingness — usually nobody looked. Nexview can say the moment something is waiting: on your phone, within seconds, with the poster attached and a link straight to the approval list.
ntfy, Gotify, Telegram and e-mail
An administrator sets the services up once. They are shared inboxes for the whole installation — deliberately separate from the bell and the personal e-mail address everybody configures in their own profile.
ntfy and Gotify you can run yourself, Telegram goes through a bot of your own. Anyone who wants none of it takes e-mail — or nothing at all, and the bell remains.
More services are meant to follow, Discord for one. What gets added depends on what people ask for — the way to ask is through the suggestions on GitHub.
Connection on top, inboxes underneath
Services with two levels get both: an ntfy server carries any number of topics, a Telegram bot any number of chats. The connection is stored once — address, token — and the inboxes underneath each pick what they want to hear about.
Per inbox you set language — one channel in German, a second in English —, urgency from quiet to high, and the events.
Six are on offer: request waiting for approval, finished downloading, decided (approved or rejected), cancelled, new ticket and feedback on a title.
So one channel can report only approvals while a second hears about everything that finishes — without anybody setting up two bots. A family channel can carry only finished downloads while the operator's channel also sees tickets.
A four-digit code decides
An HTTP 200 from a push service only means accepted, never arrived. A misspelled topic, an app with no subscription, a muted notification — all are answered politely, and you would notice only weeks later, when the first real message fails to show up.
So the test message carries a four-digit code, and only somebody who can type it back gets to save. Setting up ntfy or Telegram therefore creates connection and first inbox in one confirmed step.
E-mail targets skip the code on purpose: behind a shared mailbox or an automation there may be nobody to read it.
What happens when it jams
Underneath the channels sits an outbox with a beat of its own: every ten seconds, instead of the two minutes the rest of the sync runs on. Three attempts per message; after that the last error stays visible on the tile rather than being swallowed.
And one message per event and inbox is sent, not per recipient. A request three administrators are watching announces itself once — not three times.
The personal routes are untouched by all this: the in-app bell and your own e-mail address are configured by each person in their profile, per event. The channels described here are what the installation reports — not what an individual receives.