ClickUp Notifications Not Working? 7 Fixes for the Most Common Issues in 2026

ClickUp notifications going silent is one of the most disruptive things that can happen to a team running its entire workflow inside the platform. You miss an @mention on a client deliverable, a due date alert never fires, or a teammate marks a task complete and nobody finds out for three hours. I’ve debugged this across dozens of team setups — enterprise workspaces, agency accounts, solo operators — and the same seven failure points come up every time. This guide covers all of them with exact UI paths so you can resolve the issue in under ten minutes.

Understanding ClickUp’s three notification channels

Before jumping into fixes, you need to understand how ClickUp’s notification architecture actually works. There are three completely separate delivery channels, each with its own settings stack:

• In-app bell (⚓) — Notifications that appear inside ClickUp when you have the app open. These almost never fail because they don’t depend on the browser or OS. If in-app notifications are working but others aren’t, the problem is downstream.
• Browser push — OS-level pop-up alerts that appear even when ClickUp is minimized or in a background tab. Requires permission at three layers: the browser, the OS, and ClickUp’s own settings. All three must be enabled simultaneously.
• Email — Notification digests sent to your registered email. Configurable by frequency and event type. Subject to batching delays by default.

The critical insight: these three channels are independent. A setting that fixes email notifications does nothing for browser push, and vice versa. When a user says “notifications aren’t working,” the first question is always which channel they’re referring to.

For teams running complex workflows, notifications are closely tied to automation behavior. If you’re using automations to trigger alerts, read our complete ClickUp automations guide for 2026 alongside this post — Fix 5 below won’t make complete sense without that context.

Diagnostic table: symptom → cause → fix

Use this table to identify your specific scenario before working through the fixes.

Fix 1: Check browser push notification permissions

This is where roughly 60% of browser push failures originate. The browser itself is blocking ClickUp from sending OS-level alerts, and no amount of toggling inside ClickUp will override a browser-level block. The fix must happen at the browser first.

Chrome (most common)

1. Open Chrome and click the three-dot menu in the top-right corner.
2. Go to Settings → Privacy and Security → Site Settings.
3. Under “Permissions,” click Notifications.
4. Scroll to the “Not allowed to send notifications” section.
5. If app.clickup.com appears there, click the trash icon to remove it from the blocked list.
6. Return to ClickUp and click the bell icon → you should be prompted to allow notifications. Click Allow.
7. Verify that app.clickup.com now appears in the “Allowed to send notifications” list.

Firefox

1. Go to Settings → Privacy and Security → Permissions.
2. Next to “Notifications,” click Settings.
3. Find app.clickup.com in the list. If it shows “Block,” change the dropdown to Allow.
4. Click Save Changes.

Safari (macOS)

1. Open System Settings → Notifications.
2. Find Safari in the list and click it.
3. Ensure “Allow Notifications” is toggled on for Safari overall.
4. In Safari, go to Settings → Websites → Notifications.
5. Find app.clickup.com and set it to Allow.

Important: HTTPS requirement

A known limitation in 2026: the Web Push API used by ClickUp requires a secure (HTTPS) context. If you’re accessing ClickUp via any non-standard URL or a self-hosted proxy serving over HTTP, browser push will be silently disabled regardless of permissions. Always access ClickUp via https://app.clickup.com.

Fix 2: Enable browser push inside ClickUp’s notification settings

Even with browser permissions granted, ClickUp’s internal notification toggles must be configured separately. Many users fix the browser permission and then wonder why push still isn’t working — this is the second layer they miss.

1. Click your avatar or profile photo in the top-right corner of ClickUp.
2. Select Settings from the dropdown menu.
3. In the left sidebar, click Notifications.
4. At the top of the notifications settings page, you will see three column headers: In-App, Email, and Browser Push. Confirm the Browser Push column is visible — if it’s grayed out entirely, your browser permission from Fix 1 is not yet registering.
5. Work through each event category and toggle on Browser Push for the events you care about. The most critical ones to enable:
   • Assigned to me — fires when a task is assigned to you
   • Mentions — fires on @mention in comments or task descriptions
   • Due date reminders — fires at your configured reminder window
   • New comments — fires when anyone comments on a task you’re watching
6. Click Save if prompted (some ClickUp versions auto-save; others require an explicit save action).
7. Test by having a teammate assign a test task to you and verify the browser push appears within 30 seconds.

Note: Each user controls their own notification settings. As a workspace admin, you cannot push these settings onto teammates — they must each complete this step themselves. Direct your team to this exact path: avatar → Settings → Notifications → Browser Push column.

Fix 3: Fix email notification delays caused by batching

ClickUp batches email notifications into digest-style summaries on a 15-minute cycle by default. This means if someone assigns you a task at 9:01 AM, you may not receive the email until 9:15 AM at the earliest — or later if your mail server has its own queuing delay. For teams that use email as their primary alert channel, this delay is operationally significant.

1. Click your avatar in the top-right corner → Settings.
2. Navigate to Notifications in the left sidebar.
3. Click the Email tab at the top of the notifications panel.
4. Look for the Email Frequency setting. The default value is “Every 15 minutes.”
5. Open the frequency dropdown and select Immediately to receive email notifications as events occur.
6. Alternatively, select Every 1 hour or Daily digest depending on your preferred cadence — these are valid choices if you want reduced inbox noise at the cost of latency.
7. Save the setting.
8. Check your spam or promotions folder in your email client. ClickUp’s notification emails occasionally get caught by aggressive spam filters — add notify@clickup.com to your contacts or safe-sender list.

If you’re using ClickUp alongside other tools, delayed notifications can compound into serious workflow gaps. See our guide on fixing ClickUp integrations not syncing for related timing and sync issues that affect notification pipelines.

Fix 4: @mention notifications not arriving for recipients

This is the most common complaint I see in team environments. User A mentions User B with @username in a task comment. User B never receives a notification. The cause is almost always that User B has the “Mentions” event type toggled off in their personal notification settings.

1. The affected user (User B, the one not receiving mentions) must log into ClickUp.
2. Click their avatar → Settings → Notifications.
3. In the notification events list, locate the Mentions row (it may be labeled “Someone @mentions me” depending on your ClickUp version).
4. Verify that at least one column — In-App, Email, or Browser Push — has the toggle enabled for this event. If all three are off, mentions will be completely silent.
5. Enable the preferred channel(s) and save.
6. Test: have User A post a new comment with @UserB in a task. User B should receive the notification within the channel’s delivery window.

Additional mention troubleshooting checks

7. Confirm the @mention was typed correctly and ClickUp displayed a blue highlight around the name when selected from the autocomplete dropdown. Typed text that looks like a mention but wasn’t selected from the dropdown does not trigger a notification.
8. Check whether the user has muted the specific task (ClickUp 4.0 feature — see the Bonus section). A muted task suppresses all notifications including mentions.
9. Confirm the user is a member of the workspace or has at least guest access to the Space where the task lives. External guests with restricted access may not receive mention alerts depending on their permission tier.

For distributed teams where @mention reliability is critical, our ClickUp remote teams setup guide covers notification best practices alongside the broader communication workflow setup.

Fix 5: Automation “Notify” actions not triggering

ClickUp automations can include a “Send notification” action that pushes an alert to specified users when a trigger fires. When this silently fails, the problem usually isn’t the automation logic — it’s either the recipient’s workspace mute status or a misconfigured recipient list in the automation itself.

1. Navigate to the Space, Folder, or List where the automation lives. Click Automations in the top toolbar (the lightning bolt icon).
2. Open the automation in question and click the Notify action step.
3. Verify that the recipient field contains the correct user(s). If the automation was built by a different user, the recipient may be pointing at a role (e.g., “Assignee”) rather than a specific person — confirm the role resolves correctly for your task structure.
4. Check whether the notification type in the action is set to In-App, Email, or both. If only in-app is selected and the recipient has ClickUp closed, they may not notice it.
5. Ask the recipient to check whether they have muted the workspace. A muted workspace suppresses all automation-triggered notifications. To unmute: click the workspace name in the left sidebar → Mute workspace toggle → turn off.
6. Run the automation manually by triggering its condition deliberately on a test task. Open the automation run log (Automations → History tab) and confirm the notification action shows a green checkmark status. If it shows an error, note the error code — common causes are permission scoping issues where the automation bot doesn’t have access to notify external guests.
7. If the automation is sending notifications as part of a multi-step sequence, ensure the notification step comes after any status-change or assignment steps and not before them — order matters in ClickUp automation chains.

For a comprehensive look at how ClickUp automations interact with the notification system, including advanced trigger configurations, see our ClickUp automations deep-dive guide.

Fix 6: Mobile push notifications not working

Mobile push for ClickUp involves three separate permission layers that must all be active simultaneously. Missing any one of them results in complete silence on the device.

iOS (iPhone / iPad)

1. Open your iPhone’s Settings app → scroll down to ClickUp → tap Notifications.
2. Ensure Allow Notifications is toggled on.
3. Under alert style, select Banners or Alerts (not “None”).
4. Ensure Sounds and Badges are toggled on if you want those indicators.
5. Open the ClickUp app → tap your avatar in the bottom-left → Notifications.
6. Confirm the event types you want (assignments, mentions, due dates, comments) are enabled for mobile push.
7. Check Settings → Battery → Low Power Mode. If Low Power Mode is on, background app refresh is suspended and push delivery can be delayed or dropped entirely. Turn it off for testing.
8. If notifications still don’t appear, go to Settings → ClickUp → Background App Refresh and ensure it’s set to Wi-Fi & Cellular Data.

Android

9. Go to Settings → Apps → ClickUp → Notifications. Enable notifications and set importance to High.
10. Check Settings → Battery → Battery Saver. If battery saver is active, it aggressively restricts background processes including push notification delivery.
11. On Samsung and Xiaomi devices specifically: go to Settings → Battery → App Power Management (or “App Battery Usage”) and set ClickUp to Unrestricted. These manufacturers apply aggressive background-kill policies that intercept push notifications before they reach the app.
12. In the ClickUp app, tap avatar → Notifications and verify the in-app mobile notification toggles mirror what you want to receive.
13. Force-close the app and reopen it. Push notification tokens occasionally expire during app updates — a fresh app launch regenerates the token with Firebase Cloud Messaging.

Fix 7: Disable Focus Mode if all notifications have stopped

If you or a teammate suddenly can’t receive any notifications — not just one type, but all channels going silent simultaneously — Focus Mode is the most likely culprit. It’s easy to enable accidentally because the toggle is a single click on a prominent sidebar icon.

1. Look at the ClickUp left sidebar. Near the bottom, find the lightning bolt icon.
2. If the lightning bolt icon is highlighted or filled (indicating it is active), click it once to disable Focus Mode.
3. You should immediately see a confirmation message that Focus Mode has been turned off and notifications are re-enabled.
4. To verify: ask a teammate to assign a test task to you. You should receive the in-app bell notification within seconds.
5. If the lightning bolt icon is not visible in your sidebar, it may have been removed from view. Access Focus Mode alternatively via: avatar → Settings → Notifications → Focus Mode toggle at the top of the page.
6. If your team uses Focus Mode intentionally during deep-work blocks, create a shared understanding of when it gets enabled and disabled. Consider setting a calendar reminder to disable it at the end of focus blocks so it doesn’t carry over into the rest of the workday.

Bonus: Per-task notification muting in ClickUp 4.0

ClickUp 4.0 introduced granular per-task notification control — the ability to mute notifications for individual tasks without affecting anything else. This is genuinely useful for tasks you’re watching passively but don’t want constant alerts on. However, it’s also an easy source of confusion when a task was accidentally muted.

How to check if a task is muted

1. Open the task where notifications seem missing.
2. Click the three-dot menu (…) in the top-right corner of the task panel.
3. Look for Notification preferences in the dropdown menu.
4. In the notification preferences panel, check whether “Mute this task” is enabled. If it is, toggle it off.
5. You can also set per-task overrides here — for example, receiving email notifications for this specific task even if your global settings only send in-app alerts.

This per-task muting is separate from the workspace-level mute mentioned in Fix 5. A muted task suppresses all notification channels for that task regardless of your global settings. If your team uses ClickUp Brain AI for task summarization, note that AI-generated task updates also respect per-task mute preferences.

Frequently asked questions