You can set working hours in Slack by opening your profile menu, selecting Preferences and choosing the days and times when notifications are allowed. Slack pauses notifications outside that schedule. To communicate availability accurately, also check your status and presence: an after-hours notification schedule does not mean every signal in Slack has changed to “away.”
For a stable workweek, Slack's native controls may be enough. If you work separate morning and evening shifts, change hours for individual dates or need a late meeting to move your finish boundary, start with the same distinction: when may Slack interrupt you, and what should Slack tell colleagues?
What Slack working hours actually control
Slack separates three signals:
- Your notification settings decide when alerts reach you.
- Your status is a message and emoji explaining what you are doing or when you expect to respond.
- Your availability is the active or away indicator beside your name.
Slack now documents automatic statuses for huddles, focus mode and after working hours. It also supports statuses scheduled to start and end later. Check Preferences under Automatic statuses if you want Slack's built-in after-hours indication. The after-hours status tells colleagues when to expect a reply. Slack's status and availability guide explains these separate controls.
This matters when your laptop stays open after work. Colleagues need a clear expectation about replies, while you need a separate rule protecting notifications. Choose the signals that match the situation rather than treating a green dot as a promise of immediate availability.
Set your notification hours on desktop or mobile
On desktop, open your profile menu and select Preferences. Under Working hours, use Allow notifications to choose Every day, Weekdays or Custom, then set your start and end times. Choose Custom when different weekdays need different hours.
On mobile, open your profile, tap Notifications and find Notification schedule. Choose the days and start/end times there. Slack saves these settings automatically. The feature is available on all plans. Slack's notification instructions give the current desktop and mobile paths.
For a Monday–Friday, 9 a.m.–5 p.m. workweek, set those as the hours when notifications are allowed. You are defining the available window, rather than entering the overnight period to suppress.
If your workspace has default quiet hours, your own notification schedule takes precedence. Administrators can provide a useful baseline, but it is not a substitute for each person's local work pattern. Slack documents default DND hours separately.
Can Slack automatically set you away after work?
Away, status and paused notifications are separate settings. Slack automatically determines active or away presence from app activity; you can also change presence manually from your profile menu. Setting working hours is not the same action as setting yourself away.
For a planned absence, Slack supports scheduling a status in advance. In Update your status, choose a message and emoji, then use Duration to select a start and end time. Slack documents a limit of five scheduled statuses at once. That can cover a specific afternoon off without introducing another tool. The documented control should not be mistaken for a recurring, calendar-aware shift schedule. See Slack's scheduled-status instructions.
An integration can manage presence within Slack's API rules. The official API accepts away or auto: returning presence to Auto allows Slack to determine whether you are active. It does not force a permanent green dot. Slack's presence API reference documents that distinction.
Set Google Calendar working hours separately
Google Calendar working hours help people choose appropriate meeting times. They are a calendar availability setting, not the same configuration as Slack's notification schedule. Do not assume changing one has automatically changed the other.
On a computer, open Google Calendar settings, then Working hours or Working hours & location. Enable working hours and choose your weekly pattern. Google supports adding multiple time periods to a day. The setting is for eligible work or school accounts, and an administrator may need to enable it. Google's working-hours guide describes the requirements and controls.
For example, a 9 a.m.–noon shift and a 4 p.m.–7 p.m. shift should appear as two periods, not one ten-hour stretch. Calendar availability will then describe the actual day more clearly.
Google documents working hours as a recurring weekly schedule. A one-off appointment is therefore a different problem from changing your regular week. An out-of-office block can communicate an absence; verify its decline settings before relying on it to reject meeting invitations. Neither a working-hours warning nor an out-of-office event should be assumed to mute Slack notifications without a relevant integration.
Handle split shifts without treating the gap as work
A split shift requires two available windows and a genuine unavailable interval. Consider someone working 9 a.m.–noon and 4 p.m.–7 p.m. Allowing Slack notifications from 9 a.m. until 7 p.m. also allows them during the four-hour gap.
Slack's documented Custom notification schedule specifies a start and end time for each day; the instructions do not describe adding a second notification window to that day. Check the controls available in your workspace before assuming they can represent a split shift.
If your Slack schedule cannot represent both windows, a practical native approach is to use the wider notification window and pause notifications manually during the gap. This requires remembering the pause and return. A status saying “Back at 4 p.m.” clarifies expectations, but should not be treated as the notification pause itself.
For a recurring pattern, ModePilot's flexible work schedules support multiple work windows per day. You can define the morning and evening windows, then configure the outside-working-hours behavior for the interval between them. Depending on the settings you choose, that boundary can set Slack presence to Away, apply DND and display an appropriate status. Returning to a work window lets the automation evaluate the current schedule and calendar context again.
The important choice is whether the gap is genuinely time off. If you expect to answer messages throughout the interval, a protected boundary may misrepresent your availability. Configure the real expectation rather than using a split shift merely to make the calendar look tidy.
Make one-off changes without rewriting your week
An irregular workday needs an exception with a clear end. A doctor's appointment on Thursday should not silently redefine every Thursday afterward.
ModePilot supports date-specific schedule exceptions as well as regular weekly windows. Set the affected day's work windows instead of changing the standing week. For an immediate change, manual overrides provide temporary work-session controls, including starting work outside scheduled hours, extending the day or ending the workday early.
For example, keep a normal 9 a.m.–5 p.m. baseline but give one date a 10 a.m.–1 p.m. and 3 p.m.–6 p.m. pattern. The two windows describe the exception; the gap remains a boundary. Test the resulting Slack status and notification behavior before relying on the setup for an important day.
If all you need is a single status message for an afternoon off, native scheduled status may be sufficient. Schedule automation becomes useful when that exception must also drive working windows and connected Slack behavior.
Put a limit on late meetings
A late meeting should not automatically turn the entire evening into an open-ended workday. Decide which calendar events are allowed to extend work, and how late that extension may run.
ModePilot provides per-day Flexible finish controls, qualifying late-work extension rules and a hard cap. Choose which events qualify for an extension. Selected mode rules can distinguish a work call from a personal event, while the hard cap limits the finish boundary. Cross-midnight work also needs the correct logical workday boundary so the late session belongs to the intended day.
A useful example is a normal 5 p.m. finish with a client-call mode permitted to extend work and a 7 p.m. hard cap. That leaves room for an occasional late call while keeping a firm finish boundary. If a call regularly takes you into the evening, adjust the standing work pattern or team expectations rather than accumulating exceptions indefinitely.
The after-hours boundaries use case explains the broader schedule model. For the reasoning behind it, read why after-hours boundaries need enforcement.
Check time zones and conflicting automation
A schedule is only useful if its hours refer to the intended time zone. Slack lets you choose a time zone or update it automatically when traveling; its notification schedule follows local time. Slack's time-zone guidance explains the settings.
For work across time zones, check Slack's configured zone, Google Calendar's settings and the zone displayed beside ModePilot's working hours. Do not assume a client's 9 a.m. means your 9 a.m. Recheck the actual local start and finish after travel or a daylight-saving transition.
If Slack's behavior does not match the day you configured, inspect each control separately:
- Compare the expected local time with the schedule's displayed time zone.
- Check whether a temporary notification pause or manual status remains active.
- Check which app is writing your Slack status and notification state.
- Review the day's exception, work-session override and applicable calendar mode.
Give one automation system responsibility for each signal where possible. Two integrations trying to set the same status can produce confusing changes even if each works as configured.
If ModePilot manages DND, test what happens when it clears notification protection while Slack's native quiet hours or a longer manual pause are also in effect. Do not assume the separate pause will always be preserved. Review the automatic DND settings and choose which system should control that boundary.
Start with native working hours for a stable week. Add calendar and schedule automation when you need explicit split windows, date exceptions or controlled finish changes. The goal is for Slack to communicate the workday you actually intend to have.
Within those work windows, meeting notification protection handles calls that move. For leave spanning more than an ordinary evening, use the Google Calendar out-of-office guide.
