Scheduling quiet hours in elementary OS

elementary OS includes a Do Not Disturb mode that keeps desktop notifications from interrupting whatever you are doing. It is useful for focused study sessions, shared family computers, late-night work and periods when the messages in your inbox can wait. The practical part is deciding when the setting should change automatically, rather than remembering to switch it on every day.

The available controls depend on your elementary OS release. Some versions expose a straightforward manual switch, while others may provide additional scheduling options through updates. If your Notifications panel has no time-based setting, a user-level timer can automate the same switch without installing a complete application-control suite.

What Do Not Disturb actually controls

Do Not Disturb is a notification policy rather than a master mute button. It stops banners from appearing across the desktop, allowing messages and reminders to remain in the message list until you are ready to inspect them. It does not automatically pause music, lower the system volume or prevent an application from producing its own sound.

That distinction matters during a video call or screen-sharing session. A meeting application can still ring even though ordinary desktop banners are hidden, so the meeting controls need their own attention. Likewise, an urgent alert from a separate application may behave differently from an ordinary chat message. Quiet hours reduce interruptions; they do not guarantee that the computer will make no sound at all.

Quiet hours also differ from revoking an application's notification permission. If a particular program should never display notifications, change its individual preferences in Settings. Use Do Not Disturb for changing periods and permissions for permanent boundaries. On a shared household computer, notification previews deserve special attention because a brief banner can still reveal a private message.

Turning on quiet hours for the current session

Open Settings, select Notifications and enable Do Not Disturb. The exact arrangement varies slightly between elementary OS releases, and some installations also place a switch beside the clock in the top panel. Whichever route you use, confirm that the setting visibly shows as active before relying on an automated schedule.

A simple test is to request a message from a phone or another computer while the banner is suppressed. You should be able to find it later in the message list without seeing it cover part of the screen. The same test is useful for a calendar reminder, since calendar applications may have their own notification and sound settings.

Turning the mode off restores ordinary banners immediately, without restarting the desktop. Your choice remains attached to your user account, but it applies only while you are using that account. It does not change notification permissions on another computer, another Linux user account or the login screen.

Building a schedule around your Australian day

A useful schedule starts with a fixed commitment instead of an arbitrary number of quiet hours. A student attending a 9:00 a.m. class in Sydney might protect the period from 22:30 to 06:30, while someone working from a Melbourne office may want a quieter lunch break from 12:30 to 14:00. A tradesperson following a roster needs a different window each week, which is why fixed daily timers cannot cover every Australian work pattern.

Time-zone differences deserve attention. A meeting scheduled for 9:00 a.m. in Sydney begins at 7:00 a.m. in Perth, and Adelaide usually runs half an hour ahead of Sydney and Melbourne. These differences become particularly noticeable when a support shift crosses state borders or when a family member joins an online meeting from another city. A schedule based on the desktop's displayed time can otherwise surprise everyone involved.

Daylight saving also changes the relationship between a fixed clock time and the actual amount of sleep you receive. Sydney and Melbourne move their clocks forward on the first Sunday in October and back on the first Sunday in April. Brisbane, Perth and Adelaide remain on standard time through those changes. Scheduling with a named Australian time zone lets the timer follow local daylight saving rather than retaining a stale UTC offset.

Work calendars, shift rosters and school messages commonly converge in the same notification centre. Australian households may use Google Calendar, Microsoft 365, workplace rostering apps and calls through Telstra or another mobile network. Keep an expected school-pickup change or family emergency visible through an agreed channel, and place notification filtering around those priorities. Weekday rules also need occasional exceptions because public-holiday dates differ between states.

Automating the switch with user timers

The desktop setting is a simple value: false suppresses banners and true restores them. You can test the mechanism in your normal desktop session with gsettings set org.gnome.desktop.notifications show-banners false. The matching command uses true to reverse it. This changes the same underlying preference as the graphical switch, so there is no separate background application to install.

Systemd user timers provide a dependable way to run those commands at chosen times. They operate under your own account, require no root privileges and avoid the environment problems that sometimes affect scheduled desktop commands. The following pair enables banners at 21:30 and restores them at 06:30 in Sydney local time.

Create the directory ~/.config/systemd/user, save the following text as quiet-hours-on.service and quiet-hours-on.timer, and repeat the pair for the morning restoration:

# quiet-hours-on.service
[Unit]
Description=Enable elementary OS quiet hours

[Service]
Type=oneshot
ExecStart=/usr/bin/gsettings set org.gnome.desktop.notifications show-banners false

# quiet-hours-on.timer
[Unit]
Description=Start quiet hours at 21:30

[Timer]
OnCalendar=*-*-* 21:30:00 Australia/Sydney
Persistent=true

[Install]
WantedBy=timers.target

For the second pair, name the files quiet-hours-off.service and quiet-hours-off.timer, change the descriptions accordingly, and use true in the service command. Set the timer's OnCalendar value to *-*-* 06:30:00 Australia/Sydney. Replace Australia/Sydney with the appropriate named zone for your location, such as Australia/Brisbane, Australia/Perth or Australia/Adelaide.

Reload the user configuration and activate both timers with systemctl --user daemon-reload, followed by systemctl --user enable --now quiet-hours-on.timer quiet-hours-off.timer. The Persistent=true option helps the system apply a missed transition after the computer starts again. You can review future activations with systemctl --user list-timers.

Choosing boundaries that suit your routine

Write down the periods during which interruptions are genuinely unwelcome. For many households, that means shielding the first part of the working day, protecting a shared evening and allowing a short window for family or sporting messages. A parent might keep 21:30 to 06:30 quiet during school nights, then permit calendar alerts from 07:00 onwards so the morning routine is not disrupted.

The boundaries should reflect your attention rather than an arbitrary standard. A person who works night shifts may need the quiet period during daylight hours instead, while a remote worker might want banners suppressed during the morning and restored for the afternoon. If you use a calendar to block focus blocks, remember that the operating system's timer cannot infer your availability from every calendar application. Confirm which application actually raises each notification.

Rostered work requires a different strategy. You can change the timer temporarily with systemctl --user disable --now quiet-hours-on.timer and reactivate it when the next shift begins. Alternatively, create another timer profile with matching start and end times. Keeping the accounts and time zones explicit makes it easier to maintain when a roster crosses a daylight-saving boundary or a public holiday.

Testing the schedule and keeping control

Leave one scheduled transition running long enough to observe it. The following morning, check whether banners stayed hidden overnight and reappeared after the restoration time. During testing, avoid repeatedly changing the switch manually, because the next timer activation will set the stored value again and remove evidence of any conflict.

If nothing changes, systemctl --user status quiet-hours-on.timer will show whether the timer is waiting for its next activation. The command journalctl --user -u quiet-hours-on.service displays the service's recent output, including any failure to run the setting command. Also check that you are logged into the same desktop account that created the timer.

Continuing notifications can have other causes. Review the relevant application's permission, any separate alert category and preview settings. Lock-screen notifications are governed by their own privacy controls. If menu names or timer details differ on your release, release notes and user experiences at the elementary OS community site can help you compare working arrangements.

Starting a reliable quiet-hours routine

A dependable setup has three layers: the manual switch for immediate needs, timers for predictable periods and per-application permissions for things that should never interrupt. This combination remains useful when the schedule changes, because you are not relying on a single automation to handle every situation.

Manual control suits occasional demands such as a short meeting. Timers suit stable routines such as waking up in Sydney or Perth without a message banner appearing over the clock. For rotating rosters, keep separate profiles and disable the irrelevant timer until the next shift.

Open Settings tonight, enable Do Not Disturb and note the two times you want your first quiet period to begin and end.