Chrome and Edge Notification Settings for the Console
If your team runs the Velaro console in a browser tab rather than the Velaro Desktop app (KB 193), a few browser settings control whether chat alerts reach you when that tab is in the background. The desktop app removes this category of setting entirely by running outside the browser, which is why we recommend it for teams that depend on reliable alerts. If you're staying in the browser, here's what to set.
Google Chrome
Notification permission
Go to chrome://settings/content/notifications (or Settings > Privacy and security > Site settings > Notifications) and check that the Velaro console domain sits on the "Allowed to send notifications" list, not blocked.
Memory Saver exception
Chrome's Memory Saver feature frees up resources by putting background tabs to sleep, which can delay activity in that tab. Under Settings > Performance, add your Velaro console domain to the "Always keep these sites active" list so it stays live even when the tab isn't in focus.
Microsoft Edge
Notification permission
Go to edge://settings/content/notifications (or Settings > Cookies and site permissions > Notifications) and verify the Velaro console domain is allowed.
Sleeping tabs exception
Edge's Sleeping tabs feature works the same way as Chrome's Memory Saver. Under Settings > System and performance, add your Velaro console domain to the "Never put these sites to sleep" list.
Windows notification settings
Windows' own Focus Assist and notification controls sit above the browser and can hold back an alert regardless of what's configured inside Chrome or Edge. Check Settings > System > Notifications and Focus Assist to confirm your browser is allowed to show notifications and that Focus Assist isn't active during your shift.
Why we still recommend the desktop app
Browser vendors adjust background-tab and notification behavior on their own release schedule, without coordinating with any application that depends on it, including Velaro. A setting that works today can change in a future browser update with no warning. The Velaro Desktop app (KB 193) sidesteps that entirely by running as its own process, independent of any browser's background-activity policy, so your alert behavior stays the same release after release.
Was this article helpful?