Tuning app-specific notifications on elementary OS

elementary OS treats notifications as a deliberate, polished part of the desktop rather than an afterthought. The Pantheon desktop environment, with its Gala compositing window manager and Wingpanel indicator tray, delivers alerts through a system service that respects the freedesktop.org notification specification while adding its own visual restraint. For most users, this means a tidy banner slides in from the top of the screen, the icon collects in the notification centre, and the badge count ticks up in the wingpanel — all without the visual chaos that plagues some other platforms. Understanding the layers beneath that simple experience is the first step toward making notifications work for you instead of against you.

Per-app configuration sits at the heart of a calm, productive desktop. Whether you are chasing down an urgent message in a work chat, silencing a noisy mail client, or making sure a backup tool never interrupts a video call, elementary OS exposes enough switches to handle each case. This walkthrough covers the notification settings panel, the granular controls for individual applications, banner and sound behaviour, do-not-disturb scheduling tuned to Australian working hours, and the common gotchas that trip up Flatpak and native packages alike.

How Pantheon delivers alerts under the hood

Every notification you receive on elementary OS passes through a small but well-defined pipeline. An application sends a request over DBus to the notification daemon, which then decides how to present it based on your saved preferences. Gala handles the on-screen rendering, while Wingpanel keeps the count of unread items and surfaces the notification centre when you click. The system also relies on a small persistence service, sometimes referred to as the notification store, that remembers which alerts you have already dismissed so they remain searchable from the notification centre.

This architecture differs from GNOME's, where the same plumbing is wrapped in a more sprawling interface. elementary OS intentionally trims the surface area, presenting fewer toggles in System Settings but exposing the most useful ones — per-app banner behaviour, lock screen visibility, and sound playback — in a single, scannable list. The trade-off is that some advanced knobs, such as urgency thresholds and category-based filtering, are not surfaced in the GUI; you will need to drop into dconf-editor or tweak per-application config files for those.

Finding the notification panel and what it lists

Open System Settings from the dock or by pressing the Super key, then choose Notifications from the sidebar. The panel shows a global toggle for the notification system, a do-not-disturb option, and a list of every application that has registered itself for alerts since the last fresh install. If an app is missing from the list, it usually means it has not yet sent a notification — you can trigger one by, for example, receiving a message in a chat client, and the entry will appear on the next visit.

The Australian context matters here for a couple of reasons. Many users grab their initial copy of elementary OS from an overseas mirror, so the system clock may default to UTC after install rather than Australian Eastern Standard Time. If you have not selected your timezone in System Settings → Date & Time, scheduled do-not-disturb rules can fire at the wrong hour, especially during daylight saving transitions between AEST and AEDT. Setting the timezone to Australia/Sydney, Australia/Melbourne, Australia/Brisbane, Australia/Adelaide, Australia/Perth, or Australia/Hobart before you configure notifications will save you a debugging headache later.

Customising preferences for individual apps

Click any entry in the application list to reveal its individual settings. The available controls are similar across most apps, though the exact wording varies. You will typically see toggles or checkboxes for the following behaviours:

• Show banners: enables the on-screen pop-up that appears briefly at the top of the monitor.
• Show in notification centre: keeps the alert visible after dismissal so you can return to it later.
• Show on lock screen: displays the alert while the session is locked, useful for messaging and calendar reminders.
• Play sound: triggers an audible cue along with the banner.
• Show badge count: increments a small number next to the app's icon in the dock or wingpanel.

For a typical Australian remote worker, the most useful split is usually this: keep banner and sound enabled for chat and calendar apps so you never miss a meeting reminder, but disable banners and sound for things like package updaters or backup utilities that produce routine status pings throughout the arvo. If you are a student at a university such as UNSW or the University of Melbourne, you might also want to mute the assignment-grading portal or library catalogue alerts during lectures, leaving only the badge count so you can scan them later between tutorials.

Some applications, particularly those installed as Flatpaks, expose slightly different wording — for example, "Allow notifications" and "Show content in banner" instead of the usual elementary OS labels. The underlying behaviour matches, but it is worth knowing why two similar-looking rows in the list might offer different granularities. Snaps, which are less common on elementary OS but used in some enterprise rollouts, sit in their own section because they notify through a confined portal and ignore most of the system-level toggles.

Banner style, sound, and lock-screen behaviour

Banner presentation is handled by Gala using a theme-aware style that picks up the accent colour of your current wallpaper and GTK theme. You cannot directly customise banner timeout from the System Settings GUI, but you can install dconf-editor from the AppCentre and navigate to org.gnome.desktop.notifications to tweak the timeout, the location of the banner (top versus bottom), and whether the alert waits for user input before auto-dismissing. For most users, the defaults work well, and the only adjustment worth making is shortening the timeout if you find banners linger too long during screen sharing or video calls.

Sound selection lives under System Settings → Sound, where you can pick a system-wide alert tone or replace it with a custom .ogg file. elementary OS does not currently expose per-app sound overrides — every app that has the "Play sound" toggle enabled will use the same tone. If you need finer control, the GNOME Tweaks tool can rename the built-in sound theme files inside /usr/share/sounds, but this is a hacky workaround and will be reverted on the next system update.

Lock-screen behaviour is the most important switch for people who use a laptop on the move. Showing notifications on the lock screen is convenient, but if you carry the device to client sites, libraries, or even just the servo, you probably do not want message previews visible to anyone glancing over your shoulder. Disable "Show on lock screen" for chat and email apps and leave it on for system alerts like low battery or firmware updates, which are useful even when the device is closed.

Do-not-disturb and focus modes that suit the working day

The global do-not-disturb toggle at the top of the Notifications panel silences every banner, sound, and badge update across the system in one click. It also collapses the notification centre so that nothing new slides in until you turn it back off. For ad-hoc silencing during a meeting or a deep-work session, the toggle is exactly what you need.

elementary OS 7 and later also expose scheduled do-not-disturb windows, which you can configure through dconf-editor at org.gnome.desktop.notifications. The typical Australian schedule is something like 9 am to 5 pm during the working week, with a longer window overnight. Because the schedule uses the system timezone, double-check that you have selected Australia/Sydney or the equivalent for your state — otherwise, daylight saving changes can push the rule forward or back by an hour each October and April. Brisbane and Perth, which do not observe daylight saving, will stay rock-solid year-round, while Adelaide, Hobart, Melbourne, and Sydney will shift.

For people who work in regulated industries or simply value privacy, a small Linux User Group in your nearest capital — LUV in Melbourne, SLUG in Sydney, or BLUG in Brisbane — often runs informal sessions on hardening elementary OS, including notification policies. Dropping into one of those meetups is a fair dinkum way to learn tricks that do not make it into the documentation, and you will pick up scripts that automate focus-mode toggles based on calendar events or fullscreen applications.

Troubleshooting common notification issues

If an app refuses to show up in the notifications list, the most likely cause is that it has not yet sent an alert. Trigger one — by sending yourself a test message, for example — and reload the panel. If the app still does not appear, check whether it is installed as a Flatpak or Snap, because those containerised packages use a separate portal and may need explicit permission granted through Flatseal or by editing the Flatpak's filesystem and notification overrides.

Banners that appear but disappear too quickly, or that never appear at all, often point to the Gala compositor crashing or being restarted. Run gala --replace & in a terminal to reset it without logging out. If sounds have stopped working entirely, verify that the system's sound output is not muted and that PipeWire or PulseAudio is running. Finally, if a particular app is misbehaving — say, Evolution sending alerts to the wrong account — log out and back in; the notification daemon refreshes its app registry on session start, which clears most stale state.

The quickest way to see whether all of this plumbing is working is to open System Settings → Notifications, find your most-used messaging or mail client, and disable the banner for it. Within a minute you should notice that alerts still arrive quietly in the notification centre without the on-screen pop-up. From there, work through the rest of your apps in order of how distracting they are, and you will have a notification setup that respects your focus time without hiding the things that genuinely matter.