Repository navigation
Fixes admin-1328 - Document web push notification requirements - #935
Merged
Merged
Conversation
ArtifactsProduced during runtime |
Contributor
Author
The external connections list on the proxy and connections page tells operators which addresses Zammad has to reach. Web push notifications add another destination: the push service of the agent's browser. Add a Web Push Notifications section with the addresses of the push services, the note that the proxy and no-proxy configuration applies to them, that Zammad needs no configuration (the VAPID key pair is generated once per installation and a change invalidates every device subscription) and that the vendor push service delivers the messages. Verified against origin/develop of zammad/zammad: - app/models/push_subscription.rb:11 (PUSH_SERVICE_DOMAINS; subdomains accepted, subscriptions of other push services rejected) - app/services/service/user/push_subscription/deliver.rb:7 (TTL of one day), :83 (proxy and no-proxy list of the instance via UserAgent::HttpClient) - db/migrate/20261008110019_web_push_vapid_keys.rb:8 and db/seeds/settings.rb:6582 (generated key pair, protected setting) - app/frontend/apps/mobile/sw/sw.ts:69 (iOS ignores the push tag and stacks the notifications of one ticket) Relates to zammad/zammad-admin-documentation#1328
Web push does not require the mobile view to be installed as an app in general. The frontend reports the install reason as 'not-installed' only for Apple mobile devices without a standalone app, on Android a supported browser can receive the notifications as well. Also fix a British spelling of 'optimization' in the same section.
ralf401
force-pushed
the
rsc/fixes/admin-1328
branch
from
October 13, 2026 09:34
9637889 to
53feedf
Compare
suelje
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The external connections list on the proxy and connections page tells operators which addresses Zammad has to reach. Web push notifications add another destination: the push service of the agent's browser.
Add a Web Push Notifications section with the addresses of the push services, the note that the proxy and no-proxy configuration applies to them, that Zammad needs no configuration (the VAPID key pair is generated once per installation and a change invalidates every device subscription) and that the vendor push service delivers the messages.
Relates to zammad/zammad-admin-documentation#1328