Troubleshooting: Loom “Do Not Disturb” failing to block notifications

When Loom’s “Do Not Disturb” (DND) feature fails to block incoming notifications, popups from applications like Slack, Microsoft Teams, and Outlook continue to appear on screen during active recordings. This issue occurs when Loom lacks the system-level accessibility permissions required to trigger OS focus modes, when communication apps use proprietary in-app overlay windows rather than native operating system banners, or when recording via the browser extension instead of the desktop client.

Fast Fix

Switch from the Loom Chrome extension to the Loom Desktop App, as browser extensions cannot control system-level notification states. On macOS, grant Loom permission under System Settings > Privacy & Security > Accessibility. On Windows, open Settings > System > Focus, and ensure priority lists are not configured to bypass Do Not Disturb for background apps like Slack and Teams.

---

Diagnostic Snapshot

Parameter	Operational Detail
Failure Layer	OS API bridge failure (WinRT Focus Assist / macOS Focus API) or app overlay bypass
Affected Platforms	Windows 10/11, macOS (Ventura, Sonoma, Sequoia)
Component Required	Loom Desktop Client (Chrome Extension cannot trigger OS DND)
Impact	Sensitive notifications exposed on recordings; ruined software presentations

---

Why Do Not Disturb Fails During Recording

Loom’s DND toggle does not directly silence each app on your computer. Instead, it sends an instruction to your operating system’s global notification manager:

[Loom Desktop App Starts Recording]
                 │
                 ▼
     (Triggers DND Command)
                 │
       ┌─────────┴─────────┐
       ▼                   ▼
[macOS Focus Mode]   [Windows Focus/DND]
       │                   │
       ▼                   ▼
Suppresses Native    Suppresses Native
Action Center Toasts Action Center Toasts

This integration breaks down in four specific scenarios:

1. Using the Chrome Extension: Chrome extensions run in a sandboxed browser environment. The Loom Chrome extension has no programmatic access to your operating system’s notification center.
2. Proprietary (Custom) Notification Banners: Apps like Slack, Discord, and Teams give users an option to use “In-app notifications” instead of “macOS / Windows Action Center notifications.” Because in-app notifications are custom floating application windows, the operating system does not recognize them as system banners, rendering OS-level DND completely useless.
3. Missing macOS Accessibility Permissions: On macOS, third-party applications cannot suppress notification alerts or alter Focus modes without explicit Accessibility access.
4. Windows Priority List Overrides: Windows Focus Assist has a “Priority List” that allows specific apps (frequently Outlook and Teams) to punch through any active DND session.

---

Step-by-Step Resolution

Step 1: Ensure You Are Using the Desktop App

Verify your recording method:

• If you click the Loom icon inside Google Chrome’s toolbar, you are using the browser extension. The Chrome extension cannot silence your desktop notifications.
• Download, install, and record through the official Loom Desktop Application (Windows or Mac). For assistance getting the native app running properly, refer to Fix: Loom “Desktop App” stuck on “Initializing”.

Step 2: Configure Slack and Teams to Use Native OS Notifications

If communication tools use custom floating HTML/Electron banners, they will bypass system DND every time:

• In Slack:
  1. Click your profile picture in the bottom-left corner and open Preferences.
  2. Select Notifications.
  3. Scroll to Deliver notifications via…
  4. Select macOS Notification Center or Windows Action Center (do not select Slack’s built-in notifications).

1. Click your profile picture in the bottom-left corner and open Preferences.
2. Select Notifications.
3. Scroll to Deliver notifications via…
4. Select macOS Notification Center or Windows Action Center (do not select Slack’s built-in notifications).

• In Microsoft Teams:
  1. Click the three dots next to your profile and choose Settings > Notifications.
  2. Under Notification style, change from Teams built-in to Windows / Mac.

1. Click the three dots next to your profile and choose Settings > Notifications.
2. Under Notification style, change from Teams built-in to Windows / Mac.

Step 3: Grant System Accessibility Permissions (macOS)

Loom needs accessibility clearance to manage system-level focus triggers:

1. Open System Settings on your Mac.
2. Navigate to Privacy & Security > Accessibility.
3. Locate Loom in the list.
4. Ensure the toggle next to Loom is turned On. (If it is already on, toggle it off and back on to refresh the authorization token).
5. If drawing overlay tools or other system hooks are also acting sluggishly on macOS, check Fix: Loom “Canvas” Drawing tools lagging on macOS.

Step 4: Configure Windows 11 Focus Assist Exceptions

Prevent Windows from letting background apps punch through your active recording:

1. Open Settings > System > Focus (or Notifications > Do Not Disturb).
2. Click Set priority notifications.
3. Under the Apps section, review the list of programs authorized to override DND.
4. Remove Slack, Teams, Outlook, and web browsers from the priority list.
5. Check your Windows auto-rules: make sure Priority Only is not overriding your global settings during specific screen-sharing activities.

---

Final Verification Checklist

Before starting an important client demo:

1. Launch the Loom desktop app and verify Do Not Disturb is checked under preferences.
2. Start a test recording.
3. Check your OS status bar:
   • macOS: Look for the crescent moon icon in the menu bar.
   • Windows: Look for the bell or moon icon in the system tray turning solid.
4. If your recording system continues to crash or drop notifications into video feeds when using the browser, consider transitioning away from the web workflow by reviewing How to Resolve: Loom “Chrome Extension” crashing during Capture.