Notion workspace invitations are landing in your recipients’ spam folder instead of their inbox. This happens because email authentication records on your domain are missing, incomplete, or misconfigured. This article explains why Notion’s invitation emails get flagged by spam filters and provides step-by-step fixes for both senders and recipients.
Key Takeaways: Fixing Notion Invitation Emails Landing in Spam
- Add SPF, DKIM, and DMARC records to your domain’s DNS: These three authentication records tell email providers that Notion is authorized to send email on behalf of your domain.
- Ask recipients to whitelist the @notion.so sending address: Adding the sender to the address book or safe sender list prevents future messages from being filtered.
- Check your email provider’s spam quarantine page: Some providers hold suspicious emails in a quarantine folder instead of the spam folder, which requires manual release.
Why Notion Invitation Emails Go to Spam
Notion sends workspace invitations from the email address notifications@notion.so on behalf of your domain. Email providers like Gmail, Outlook, and Yahoo use three authentication checks to decide whether an email is legitimate: SPF, DKIM, and DMARC. If any of these checks fail, the email is flagged as spam or rejected outright.
The root cause is almost always a missing or misconfigured DNS record on the sender’s domain. For example, if your domain has a strict DMARC policy (p=reject) but does not include Notion’s sending servers in the SPF record, the email fails authentication. Similarly, if DKIM signing is not set up for Notion’s sending domain, the email appears unauthenticated.
How Email Authentication Works for Notion
When Notion sends an invitation, the receiving mail server checks the following:
- SPF (Sender Policy Framework): Verifies that the sending IP address is authorized by the domain owner. Notion’s SPF include mechanism must be present in your domain’s DNS.
- DKIM (DomainKeys Identified Mail): Verifies that the email was signed with a private key matching a public key published in your DNS. Notion signs emails with its own DKIM selector.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): Tells the receiving server what to do if SPF or DKIM fails. A strict DMARC policy (p=quarantine or p=reject) will cause legitimate Notion emails to be blocked if SPF/DKIM are not set up.
If any of these records are missing, the invitation email is treated as suspicious and routed to spam.
Steps to Fix Notion Invitation Emails Going to Spam
There are two sides to this fix: the domain owner (workspace admin) and the recipient. Both may need to take action.
For Workspace Admins: Configure DNS Authentication Records
If you own the domain used for the workspace, follow these steps to add the required DNS records. You will need access to your domain registrar or DNS hosting provider (such as Cloudflare, GoDaddy, Namecheap, or your web host).
- Add Notion’s SPF record to your domain DNS
Log in to your DNS provider and locate the TXT record editor for your domain. Add a new TXT record with the value:v=spf1 include:spf.notion.so ~all. This authorizes Notion’s email servers to send on behalf of your domain. If you already have an SPF record, addinclude:spf.notion.sobefore the~allor-allmechanism. - Add Notion’s DKIM record
Add another TXT record with host namenotion._domainkey.yourdomain.com(replace yourdomain.com with your actual domain). The value is:v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC6Z6QJ6z7e3+8E1qP7b5h9p4R0vL0y6W1d5c2s8pQ0vL0y6W1d5c2s8pQ==(this is a truncated example; contact Notion support for the exact public key). If you cannot obtain the key, skip DKIM and rely on SPF and DMARC only. - Add or update your DMARC record
Add a TXT record with host name_dmarc.yourdomain.com. The value should be:v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com. Start with p=none to monitor authentication failures without blocking email. After confirming that SPF and DKIM pass, change p=quarantine to send failures to spam, or p=reject to block them entirely. - Wait for DNS propagation
DNS changes can take up to 48 hours to propagate worldwide. Use a tool like MXToolbox or Google Admin Toolbox to verify that the records are visible. Resend the Notion invitation after propagation is complete.
For Recipients: Whitelist Notion’s Sending Address
If you are the recipient of the invitation and do not control the domain, you can prevent Notion emails from going to spam by adding the sender to your address book or safe sender list.
- Add notifications@notion.so to your contacts or address book
Open your email client and create a new contact with the email address notifications@notion.so. In Gmail, click the gear icon, select See all settings, go to Filters and Blocked Addresses, and create a filter that never sends email from that address to spam. - Check the spam folder and mark as Not Spam
If the invitation is already in spam, open the spam folder, select the email, and click Not Spam or Report Not Spam. This trains the filter to allow future emails from that sender. - Check the quarantine folder (Outlook/Exchange)
If you use Microsoft 365 or Exchange, spam-filtered emails may be held in a quarantine page. Go to https://security.microsoft.com/quarantine, log in, and look for emails from notifications@notion.so. Select the email and click Release.
If Notion Invitations Still Go to Spam After the Main Fix
DMARC Policy Is Too Strict
If you set p=reject in your DMARC record but SPF or DKIM are not fully configured, all emails that fail authentication will be rejected, not just flagged. Change the policy to p=none or p=quarantine until you confirm that authentication passes. Use DMARC aggregate reports to see which sources are failing.
Third-Party Email Forwarding Interferes
If the recipient uses email forwarding (for example, forwarding from a work domain to Gmail), the forwarded email may fail SPF because the original sending IP does not match the forwarder’s IP. In this case, the forwarded email is more likely to be flagged. Ask the recipient to use their primary inbox directly or set up a rule to bypass spam filtering for Notion emails.
Corporate Email Server Blocks External Senders
Some organizations configure their email server to block all emails from external domains that are not in the global allowlist. If you are sending an invitation to a corporate email address, ask the IT department to add notifications@notion.so to the allowlist. This is a server-side setting that cannot be bypassed by the recipient alone.
Email Provider Spam Handling Compared
| Provider | Spam Action for Unauthenticated Email | Whitelisting Method |
|---|---|---|
| Gmail | Sends to spam folder | Add sender to contacts or create a filter |
| Outlook.com | Sends to junk email folder | Add sender to safe senders list |
| Microsoft 365 | Sends to quarantine (admin can release) | Admin adds domain to allowlist in Exchange admin center |
| Yahoo Mail | Sends to spam folder | Add sender to contacts |
After completing the DNS configuration on your domain and whitelisting on the recipient side, Notion invitation emails should arrive in the inbox. If the problem persists, use an email authentication checker like MXToolbox to verify that your SPF, DKIM, and DMARC records are correctly published and pass validation. For recurring issues, contact Notion support with the exact email address and timestamp of a failed invitation.