Notion6 min read

Notion email notifications: do they actually reach your team?

Mentions, comments, calendar reminders — Notion relies on email to pull people back into the workspace. When those emails land in spam, collaboration quietly breaks down.

Notion has become the default operating layer for a lot of teams. Docs, tasks, roadmaps, meeting notes, wikis — all in one place. And the glue that pulls people back when something changes is email: "Anna mentioned you in Q4 planning", "New comment on Design review", "Task due tomorrow". When those messages stop arriving, Notion feels quiet. It isn't — work is happening, your team just doesn't know about it.

TL;DR

Notion sends notification mail from its own infrastructure. For most Gmail and Outlook inboxes it lands in Primary, but Workspace admins see pockets of users where mentions end up in Spam or Updates tabs. Test placement across your actual sending domains and subscribe to the Notion integration beta below.

The flavors of Notion email

Before testing anything, it helps to know what Notion actually sends. Each type has slightly different filter behaviour because headers, subjects and rendering differ.

  • Mentions — "X mentioned you". The most urgent flavor; recipients expect these in Primary.
  • Comments — new comment on a page you follow. Medium importance. Gmail sometimes buckets these as Updates.
  • Calendar reminders — upcoming page or task. Looks more calendar-y than mail and can be deprioritised.
  • Invites — invited to a page or workspace. Highest sensitivity for phishing filters because it triggers "link to external collaboration".
  • Digest / weekly summary — low urgency. Often in Promotions by design.

Where they actually land

Notion generally has strong domain reputation, so placement in personal Gmail is mostly Primary. But admins over large Workspaces consistently report issues in two places:

  1. M365 tenants with aggressive anti-phishing. Defender for Office 365 flags the combination of external sender + "click here to view page" link as impersonation risk. Mentions land in Junk for specific users.
  2. Google Workspace with custom filters. An admin rule written years ago to catch "external collaboration" mail routes Notion into a label. The team stops seeing it and no one remembers why.

How admins can verify inbox placement

If your users are complaining that they miss mentions, don't debug one mailbox — run a seed test across provider types that match your org's actual mix.

  1. Open a Notion page, mention a seed address from Inbox Check (you can use the placement-test addresses as a workspace guest or directly in comments for testing).
  2. Within seconds you'll see where the notification landed across Gmail, Outlook.com, Workspace, M365, Yahoo, Mail.ru and more.
  3. Flag which provider types send to Junk and share the report with the corresponding admin so they can whitelist the Notion sending domain (notify@mail.notion.so) at the gateway.
Notion integration in beta

A native Notion integration is in private beta. It triggers a mention from a test page, collects the resulting notification across 20+ provider mailboxes, and reports any placement drift — so you see a regression the moment Notion changes infra or your tenant tightens a rule.

→ Join the beta waitlist

Workspace settings that affect delivery

Notion exposes a handful of controls that change what goes out over email. Make sure they're configured the way your team expects.

  • My notifications → Email notifications. Per-user toggle for mentions, comments, invites. If a user has this off, nothing you do at the admin level helps.
  • Workspace settings → Members. External collaborators tend to be filtered more aggressively by their own providers. Placement depends on where they are, not where you are.
  • Slack integration. If Slack is present, consider routing mentions there instead of email. Slack notifications are not subject to spam filters and tend to be seen faster.
  • Allow-list at the gateway. Add mail.notion.so and notion.com to your Workspace or M365 allow-list if repeated Junk placement is confirmed.

Troubleshooting checklist

"I mentioned Anna but she never got an email"

First check Anna's per-user email notification settings; they default on but people turn them off during focus periods. Next, confirm Anna is a member (external guests need explicit invitation). Finally, run a seed test at Anna's provider type — if Gmail is Inbox but M365 is Junk, the issue is at the tenant gateway.

Digest emails land in Promotions

This is largely by design — digests look marketing-y. If you want them in Primary, ask a few users to open the digest and drag it to Primary once; Gmail will rethink placement for that sender.

Calendar reminders missing

Make sure the page has a date property being used as a reminder and that the user has notifications enabled for that reminder type.

FAQ

Can I send Notion notifications from my own domain?

No. Notion controls the sending domain. The closest alternative is to forward notifications into a tool you do control (Slack, a shared inbox) and reduce reliance on Notion's email path for urgent pings.

Why does one user miss mentions while others get them fine?

Almost always per-user preferences or a user-level rule in the mail client. Check notification settings in Notion, then search the user's mailbox for existing filters matching "notion".

How often should I run a placement test?

Monthly is plenty for a healthy workspace. Re-test after any major provider policy change (Gmail/Outlook tend to shift once or twice a year) and any time a user reports missing notifications.

Does Notion support DKIM on its sending domain?

Yes, Notion signs its outgoing mail. You don't need to configure anything on your side — the authentication is on their domain, not yours.
Related reading

Check your deliverability across 20+ providers

Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and more. Real inbox screenshots, SPF/DKIM/DMARC, spam engine verdicts. Free, no signup.

Run Free Test →

Unlimited tests · 20+ seed mailboxes · Live results · No account required