Making Google Chat notifications show up on a Mac

A mention landed in a space forty minutes ago. Google Chat was open in a Gmail tab the whole time. Nothing appeared on the Mac, and the phone buzzed instead, which is the opposite of useful for someone sitting at a keyboard.

That specific failure is not a broken permission. It is Google Chat working exactly as designed, choosing a different device. Understanding that choice comes before any of the settings panes, because a Mac with every permission granted can still lose the race and receive nothing.

Chat picks a device, and the Mac can lose

Google's help page on Chat notifications opens with a rule that most troubleshooting guides never mention. Notifications appear on the devices used most recently, and if the account is not active in Chat, notifications appear on all devices signed in to that Google Account.

The mechanism behind the word active is idle detection, and Google documents its threshold. Idle detection delivers notifications to the active device, and someone counts as idle after being inactive for over thirty seconds, even with a web browser still open. When idle on Gmail or Chat on the computer, notifications go to the mobile device instead.

Thirty seconds of not typing is enough to hand the next notification to a phone. Reading a document, sitting in a meeting, or thinking about a problem all qualify. That single fact explains the most common version of this complaint, in which notifications work perfectly while typing in Chat and never appear at any other moment.

The design goal is reasonable. Google describes the permission dialog in plain terms: it asks to pause mobile notifications while the person is active on that device, which is meant to stop every message arriving twice. The side effect is that a Mac only reliably receives Chat notifications when it is the device in use, unless idle detection is granted so that the two devices can coordinate properly.

The permission chain, in the order it breaks

Four layers sit between a Chat message and a banner on a Mac, and each one can stop it alone. Checking them out of order is what turns this into an afternoon.

The operating system. Google's troubleshooting page starts here, noting that each operating system has different steps and that some have settings that mute notifications entirely. On a Mac this means System Settings, then Notifications, then the application in the list. If Chat is being used in a browser tab, that application is the browser, not Chat.

The browser permission. Google's instructions for Chrome are to open Settings, go to Privacy and security and then Site Settings, scroll to Permissions and select Notifications, and find the entries for the Chat and Gmail addresses, listed as the secure addresses for chat.google.com and mail.google.com. The page adds an explicit tip: to be sure notifications are allowed, add both of those addresses under the heading for sites allowed to send notifications. Adding only one is a frequent miss, and which one matters depends on whether Chat is used standalone or inside Gmail.

The Chat setting. On the computer, open Google Chat or Gmail, click Settings at the top right and then Notifications, and under Desktop notifications find the toggle for allowing chat notifications. In Gmail the path runs through Settings, then See all settings, then Chat and Meet, then managing chat settings. Google notes that if the toggle is already on but notifications are not arriving, a Turn on button may appear, and clicking it opens a browser permission dialog that grants both browser notifications and idle detection in one step.

The conversation setting. Even with all of the above correct, a muted conversation or a Chat status set to Do not disturb produces nothing.

Granting idle detection when the prompt never appeared

The single prompt described above is the intended path, but it frequently does not appear, usually because the notification permission was granted long before idle detection existed as a separate permission.

Google documents the manual route for Chrome. Open the settings page for idle detection, tick the box for allowing sites to ask to know when the device is actively being used, and under the heading for customized behaviours add mail.google.com or chat.google.com to the allowed sites list using the Add button.

There is a second, gentler path in the same help page. On the computer, open Google Chat or Gmail, click Settings and then manage Chat settings, and under Desktop notifications, if there is a separate prompt to turn on idle detection, click Turn on and follow the browser prompts.

It is worth being clear about what this permission does and does not do. It does not make the Mac notify more. It makes the Mac and the phone agree about which of them is being used, so that one of them notifies rather than both or neither. For anyone whose complaint is duplicates rather than silence, this is the setting, and it is almost always the one that was never granted.

What Chat notifies about, and how to narrow it

Google lists the defaults, and they are narrower than people assume. By default, notifications arrive when someone mentions the account with an at sign, and when someone reacts or responds to a message from that account. A space that produces no notifications may simply be generating neither of those things.

Per space, the levels are set from the More options menu next to the space name, under Notifications. The choices are all messages and replies, main conversations covering new conversations and mentions, a setting covering mentions only, and none. For a direct message, the equivalent menu offers all or none. There is also an option to mute a conversation so it stops being pushed to the top of the list.

Three more behaviours are documented and each one answers a question that comes up repeatedly.

Applications and bots can override the settings. Google states that messages sent with the notify keyword are for critical or time sensitive information, work like messages to everyone, and ignore Do not disturb status, muted conversations and notification settings. Messages sent with the silent keyword do the opposite and behave like system messages. Only applications and bots can send either type, which means a space that keeps breaking through a Do not disturb status is not misconfigured.

Email is the backstop. If email notifications are on, Google sends email reminders for Chat messages that have gone unread for more than twelve hours.

Accounts are configured separately. Google notes that with multiple Google Accounts, different notification settings can be set for each. That is a useful capability and also a warning, since a setting fixed in one account changes nothing in the other.

When the banner appears but stays silent

A visible notification with no sound is a different fault from a missing one, and it has its own short chain. Google Chat carries a notification sounds setting of its own, in the same Notifications section as the desktop notifications toggle, so the sound can be chosen or removed there without touching anything else.

If that is set and there is still nothing audible, the remaining links are in macOS. The per application sound switch under Notifications has to be on for whichever application is delivering the alert, which for a browser tab means the browser rather than Chat. Then, in the Sound pane, the alert volume matters, and Apple's guide is explicit that alert volume is relative to the computer's output volume, so a muted or very low system volume overrides it. The output device selection in the same pane is the last link, and it accounts for the alerts that played perfectly into a headset lying in a bag.

Reading the symptom before touching a setting

What is happening	Most likely layer	What to do
Nothing on the Mac, the phone gets everything	Idle detection, and the device race	Grant idle detection so the devices coordinate
Both the Mac and the phone alert	Idle detection not granted	Same setting, different symptom
Nothing anywhere on the Mac, including test messages	The operating system or the browser permission	System Settings, then both Google addresses in Site Settings
Notifications for direct messages but not for a space	The per space level	Set the space to all messages, or to main conversations
Notifications arrive but with no sound	Sound settings	The sound choice in Chat, and the per application sound switch in System Settings
A space breaks through Do not disturb	An application using the notify keyword	Documented behaviour, not a misconfiguration

The order in that table is deliberate. The two idle detection rows cover a large share of real cases and cost one permission to fix, while the permission chain below them is slower to work through.

The standalone app changes the identity, with a catch

Everything above shares one structural problem. A browser tab holding Chat delivers its notifications to macOS under the browser's identity, together with every other site in that browser. One row in System Settings, one alert style, one sound switch and one Dock badge cover Chat, a calendar, a ticketing system and anything else permitted over the years. A Focus can allow the browser or hold the browser, and nothing finer.

Google offers a partial answer. The Chat standalone app is a Progressive Web App installed through Chrome, and Google's requirements are specific: Chrome 73 or above, installed by clicking Install in the address bar or choosing to install Google Chat from the More menu. On a Mac it then opens from the Applications folder. The important caveat is in the same page: Chrome does not need to be the default browser, but it does need to be open for the standalone app to work.

Apple's own route has a different shape. From macOS Sonoma 14 onward, Safari can save a page as a web app through File and then Add to Dock. Apple states that a web app functions independently of Safari and shares no browsing history, cookies, website data or settings with it, that its Dock icon can show the number of unread notifications, and that it can be added as a login item. Each one appears separately in System Settings, so Chat can be persistent and audible while other services stay quiet. The cost is that several services become several Dock icons with several sets of settings and nothing grouping them.

A browser that keeps each web app in its own window applies the same separation without the sprawl and without depending on another browser staying open, so a work account and a second account on the same service can be badged and silenced independently. How those separate sessions are arranged is described in Workspaces, and which services work in that shape is listed in Supported apps.

What to change first

Grant idle detection before changing anything else, because the most common version of this problem is a device race rather than a blocked permission, and a Mac counts as idle after thirty seconds of not typing. Then add both the Chat and Gmail addresses under the sites allowed to send notifications in Chrome, rather than only the one currently in use. If notifications then arrive but cannot be told apart from every other site in the browser, the settings have run out, and giving each service its own window in SpaceDeck is what makes them separate senders to macOS.