Why Notion Page Sharing With External Email Fails on Specific Domains

When you try to share a Notion page with an external email address, the invite may fail silently or return an error message only for certain domains like @protonmail.com, @outlook.com, or @company.com. This problem occurs because Notion’s email delivery system relies on the recipient’s mail server accepting messages from Notion’s sending infrastructure. This article explains the technical reasons behind domain-specific sharing failures and provides actionable steps to resolve them.

Notion uses a third-party email service to send invitation links. If the recipient’s email server blocks or rejects messages from that service, the invite never arrives. The failure is not a Notion bug; it is a mail server policy issue. Understanding this root cause helps you choose the correct fix rather than retrying the same action.

Below you will learn why certain domains cause invites to fail, how to verify the problem, and what changes you or your IT team can make to restore page sharing for blocked domains.

Why Notion Invitation Emails Are Rejected by Specific Email Domains

Notion sends invitation emails through a transactional email provider such as SendGrid or Amazon SES. These providers send emails on behalf of Notion from a shared IP range. When the recipient’s email server receives the message, it checks the sender’s domain against SPF Sender Policy Framework and DKIM DomainKeys Identified Mail records. If the sending IP address is not authorized by the recipient’s SPF record, or if the DKIM signature is missing or invalid, the server marks the email as spam or rejects it outright.

Some email domains have strict inbound policies. Free email providers like ProtonMail and Tutanota block emails from bulk-sending IP ranges by default. Corporate domains using Microsoft 365 or Google Workspace may have custom transport rules that block external invitations from collaboration tools. These rules are often created by IT administrators to prevent phishing or data leakage.

Another common cause is domain reputation. If the Notion email provider’s sending IP has been flagged for sending spam in the past, some mail servers will refuse all messages from that IP. Notion rotates IPs periodically, but a domain that previously blocked Notion may continue to do so until the recipient’s administrator updates the allowlist.

How to Confirm the Email Was Rejected

Open the Notion page and check the share history. Click Share in the top-right corner. Look for the Invite history or Pending invites section. If the invite status shows Pending for more than 24 hours, the email was likely rejected. You can also ask the recipient to check their spam folder. If the email is not in spam and the status remains pending, the mail server rejected it before it reached the recipient’s inbox.

Steps to Resolve Sharing Failures for Specific Domains

The following steps address the problem from two angles: bypassing email delivery and fixing the server-side block. Choose the method that fits your situation.

Method 1: Use the Copy Link Workaround

This method avoids email delivery entirely. You send the page link through a channel that already works, such as Slack, Microsoft Teams, or a direct message.

1. Open the page share menu
   Navigate to the Notion page you want to share. Click the Share button in the top-right corner of the page.
2. Enable link sharing
   Toggle the Share to web option on. If you want to restrict access, choose Anyone with the link and set the permission level to Can edit, Can comment, or Can view.
3. Copy the page link
   Click Copy link. The link is now on your clipboard.
4. Send the link externally
   Paste the link into an email, a chat message, or any other communication tool that reaches the recipient. The recipient clicks the link and accesses the page directly without receiving a Notion invitation email.

Method 2: Ask the Recipient to Whitelist Notion’s Sending Domain

If the recipient controls their own email server or has access to their email provider’s allowlist settings, they can whitelist Notion’s sending domains. This method fixes the root cause and allows future invites to arrive normally.

1. Identify Notion’s sending domains
   Notion sends emails from notion.so and em.notion.so. The exact subdomain may vary, but these two are the primary senders.
2. Instruct the recipient to add to allowlist
   Tell the recipient to add notion.so and em.notion.so to their email provider’s safe sender list or domain allowlist. For Microsoft 365, this is done in the Exchange admin center under mail flow > allow lists. For Google Workspace, it is in the admin console under Apps > Gmail > Spam, Phishing, and Malware.
3. Resend the invitation
   After the recipient whitelists the domains, go back to the Notion page, click Share, and resend the invite using the email address. The invite should now arrive in the inbox.

Method 3: IT Administrator Configures SPF and DKIM Records

This method applies only when the recipient domain is a corporate domain that you administer. If you are the IT admin for the recipient’s organization, you can configure SPF and DKIM records to accept Notion’s emails.

1. Add Notion’s SPF record
   In your DNS management console, add an SPF TXT record that includes Notion’s sending IP ranges. Notion provides the current SPF include value at spf.notion.so. The record should look like: v=spf1 include:spf.notion.so ~all
2. Add Notion’s DKIM record
   Notion uses DKIM signing for emails. Add the DKIM record provided by Notion’s support team. Contact Notion support and request the DKIM public key for your workspace domain if you use a custom domain for invites.
3. Test the configuration
   Send a test invite from Notion to an email address on the same domain. Wait 10 minutes for DNS propagation. Check the email headers for SPF pass and DKIM pass status.

If Notion Sharing Still Fails After Applying the Fix

Invite Status Shows Delivered but Recipient Cannot Access the Page

The recipient received the email but the link does not open the page. This usually means the recipient is not signed into the correct Notion account. Ask the recipient to sign in to Notion using the email address that received the invite. If they use a Google SSO account, they must sign in with that Google account, not a different email.

Copy Link Method Works but Recipient Sees a Blank Page

The recipient clicked the link but sees an empty Notion interface. This happens when the page is inside a private teamspace and the recipient does not have access to that teamspace. Grant the recipient access to the teamspace by going to Settings & Members > Members and adding them as a guest with the correct teamspace permissions.

Corporate Domain Blocks All External Invitations by Policy

Some organizations use a mail flow rule that blocks any email with the phrase “invites you to” or from known collaboration domains. The recipient’s IT admin must create an exception rule for Notion’s sending domain. If the admin cannot do this, use the copy link method as a permanent workaround.

Notion Invite Methods Compared: Email vs Direct Link

Item	Email Invite	Copy Link
Delivery method	Transactional email from Notion’s provider	URL copied from share menu
Requires recipient email access	Yes	No
Affected by SPF/DKIM blocks	Yes	No
Recipient must sign in to Notion	Yes	Yes
Works for blocked domains	No	Yes
Requires manual link sharing	No	Yes

Notion page sharing with external email fails on specific domains because the recipient’s mail server rejects emails from Notion’s sending infrastructure. The most reliable fix is to use the copy link method, which bypasses email delivery entirely. If you need email invites to work, ask the recipient to whitelist notion.so and em.notion.so or configure SPF and DKIM records if you control the domain. After fixing the block, resend the invite from the share menu. For corporate domains with strict policies, the copy link method remains the only guaranteed solution.