How to Share Notion Pages With Claude

To share Notion pages with Claude, you connect your Notion workspace through Claude's built-in connector and select which pages Claude is allowed to read. Claude can then reference those pages in your conversations without you copying and pasting the content each time.

The connection is read-focused: Claude reads what you authorize. It does not have access to the rest of your Notion workspace, and it does not edit pages through the standard connector setup. Tools like fenbs complement Notion by holding the decisions and shared work context that change faster than any wiki page.

Authorize Notion access in Claude

Start in Claude.ai. Open Settings and find the Integrations section. Notion appears in the list of available connectors. Click Connect, and Claude will redirect you to Notion's authorization screen where you sign into your Notion account and choose what Claude can access.

During authorization, Notion asks which pages or workspaces to share with the connected app. You choose at this point whether to give access to a specific page, a section, or a broader selection. You can come back and change this later through Notion's own Connected Apps settings.

Once authorized, the connection appears in Claude's Integrations settings. You can disconnect it there or manage access levels. The actual page selection happens on Notion's side, not Claude's.

Choose which pages to share

Be selective about which pages you authorize. Claude can read all the content in the pages you select, including any sub-pages nested within them. A top-level workspace page with hundreds of nested documents gives Claude a large amount of content to work with—some useful, some not.

A useful starting selection might include the project overview, the team handbook, a list of active projects, or any reference document Claude will need to cite in answers. Leave out personal notes, draft content that is not ready to be referenced, or archives that are no longer current.

• Select pages whose content you would actually paste into a prompt—those are the ones worth sharing.
• Avoid sharing sub-pages you have not reviewed; nested permissions can be wider than expected.
• If you share a database, check whether Claude will see its full contents or a filtered view.
• Keep the selection small enough that you can describe it: "Claude can see our project wiki and the team handbook."

Verify what Claude can actually read

After authorizing, test the connection in a real conversation. Ask Claude about something specific in a page you shared: "What does the project brief say about the target audience?" A correct answer confirms Claude can read the page. If it cannot find the content, the page may not have been included in the authorization, or the connection may need to be refreshed.

You can also ask Claude directly: "Which Notion pages can you see?" A well-configured connector should be able to list the top-level pages it has access to. If it returns nothing or an error, revisit the authorization in both Claude's Integrations settings and Notion's Connected Apps.

Notion databases and pages that use complex formatting—embedded synced blocks, inline formulas, or linked databases—may not be read perfectly. Test with the actual pages you plan to reference before building a workflow around them.

If Claude returns content that does not match what you see in Notion, the authorization may have lapsed or the page selection may have changed. Revisit Notion's Connected Apps settings, confirm that the page is still shared, and reconnect if needed. In some cases, starting a fresh conversation causes Claude to re-read the page and pick up recent changes.

What the connector does and does not do

The standard Notion connector for Claude supports reading. Claude can reference, summarize, and answer questions about the pages you shared. It does not create new Notion pages, edit existing ones, or add database entries through the standard connector. Assume read-only unless you have tested a specific write action and confirmed it works.

The connector also does not sync in real time. If you update a Notion page after the connection is established, Claude may not see the latest version immediately. For content that changes frequently, treat Claude's answer as a starting point and verify against the live Notion page before acting on it.

How to do this with fenbs

1. Create a free account and add a project to your fenbs board with a short description of what it is trying to achieve.
2. Authorize Notion in Claude and select the pages relevant to that project, following the steps above.
3. After your first session using Notion content, record the key decisions it produced in fenbs Decisions and rules—link to the relevant Notion page in the decision note.
4. Connect Claude via MCP from Integrations. Claude reads the fenbs work context alongside the Notion pages, giving it both the reference material and the current decisions.
5. When Notion pages are updated, re-verify Claude's understanding of the key facts before the next session that depends on them.