How to Connect Multiple Notion Workspaces to Copilot
Copilot’s Notion connector is read-only and holds one workspace per user, so Carly is where a second workspace and any write action have to live. Notion issues one authorization per workspace, Microsoft exposes one Connect action with no account picker, and Microsoft documents the federated connector as read-only. Authorize each workspace in Carly and one instruction can read or write in whichever one you name. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
1. Add your Notion workspaces to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Notion, click Connect, and authorize the workspace.
- Click Connect again for the next one, and keep going for as many workspaces as you want.
If your company runs Notion Enterprise, admins there can restrict which AI apps members connect to an approved list, so approval may need to happen once on the Notion side. Notion also states it cannot revoke tokens for tools connected previously, which is worth knowing before you audit old connections.
Carly connects to thousands of apps, so while you are on that page you can add your inboxes, calendars, CRM, and anything else you want Copilot to reach through the same connector.
2. Choose how Copilot reaches Carly
Copilot has no box where an ordinary user pastes a connector URL, on either SKU. Consumer Copilot at copilot.com ships a fixed connector list and its support page never mentions MCP. Microsoft 365 Copilot, the paid work SKU, accepts an MCP Base URL only from an administrator. That is Microsoft’s connector model rather than a gap on Carly’s side, and it leaves three honest routes.
You work with Carly directly. The workspaces you connected at step 2 are usable immediately, and writing across them is the point. Most readers stop here.
A maker adds Carly in Copilot Studio. This is the Microsoft-side route that actually fits Carly, because it carries write actions. Tools → Add a tool → New tool → Model Context Protocol, then supply a server name, a description, and https://carlyassistant.com/mcp/ as the server URL, with auth set to None, API key, or OAuth 2.0. Only Streamable transport is supported; SSE was dropped in August 2025. It needs a work or school account and a paid licence, the trial cannot publish the agent, and it produces a separate agent rather than Copilot Chat.
An administrator adds a federated connector, which is a partial fit. Microsoft 365 admin center → Copilot → Connectors → Gallery → Create a new connector, then under Connect to MCP server select Add and fill in a display name and Base URL. It needs the Global Administrator or AI Administrator role plus a registered Entra SSO or OAuth 2.0 application, and Microsoft requires these connectors to be read-only, so an admin gets a read slice rather than page creation. Federated connectors reached general availability in June 2026 and admin center management shipped in July 2026.
If none of those shapes fits your team, the API and bring-your-own-key path runs through the Carly team. Book a call to scope it.
What one chat can do afterwards
- Compare a client’s security questionnaire against your standard answers page.
- Say which workspace each answer came from, in one reply.
- Create a kickoff page in the client workspace.
- Flip a database property in the company workspace on the same instruction.
- Reach a personal workspace and a company one side by side.
- Act when a row moves, rather than when you remember to check.
Nothing is merged. Each workspace stays separately authorized, and Carly keeps them individually addressable.
Two workspaces: the actual wall
Notion issues one authorization per workspace. Notion’s own help documentation states that connections are workspace-specific and tells you to click the workspace name at the top right to switch to another one, and the OAuth response carries a single workspace ID identifying where the authorization took place.
| What you need to reach | Situation | Native path |
|---|---|---|
| Your company workspace | The one you connect | Read-only |
| A teamspace inside it | Same workspace | Read-only, with your Notion permissions |
| A database shared with you | Same workspace | Read-only, once you can open it in Notion |
| Your personal Notion | Second workspace | Not natively |
| A client’s workspace | Second workspace | Not natively |
What the one native connection still gives you
If a single Notion workspace covers your work and you only want to read it, the federated connector is worth the minute it takes. Notion is listed by name in Microsoft’s federated connector documentation, and once connected Copilot reaches what your Notion account can already open inside that workspace: teamspaces, shared databases, pages you were invited to. Microsoft states that federated connectors access data using the user’s identity and permissions.
It also uses Model Context Protocol to fetch data in real time rather than indexing into Microsoft 365, so nothing is cached in your tenant, a page edited two minutes ago reads correctly, and a page you lose access to stops appearing immediately. The surfaces are narrower than people expect: Microsoft 365 Copilot Chat, Copilot in Excel, and the Researcher agent, not everywhere the Copilot name appears. Microsoft-published federated connectors are enabled by default for a tenant unless admins disable them, after a seven calendar day admin review window, so a missing Connect button means an administrator turned it off.
That covers one workspace, read-only. The second workspace and every page you wanted created are outside it, which is where step 2 above starts earning its keep.
Native Copilot versus Carly
| Need | Microsoft 365 Copilot | Carly |
|---|---|---|
| Read pages in one Notion workspace | Yes | Yes |
| Respect your Notion permissions | Yes | Yes |
| Keep Notion content out of a tenant index | Yes, nothing is indexed | Yes |
| Hold two workspaces at once | No | Yes |
| Create a page or update a database property | No, the connector is read-only | Yes |
| Act when a page or row changes | No | Yes |
Carly authorizes per workspace on your side, several at once, so a personal workspace and a client workspace sit alongside the company one without a tenant project or a Premium licence. It writes, including database properties, and it fires on the event rather than on a prompt: a row moves to Blocked and the owner gets the email, the client gets the status note, and the calendar gets the check-in.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Notion.
Quick fixes
| Problem | Fix |
|---|---|
| Notion is missing from Copilot’s data sources | An admin has disabled the connector, or the seven day review window has not elapsed |
| A page in the connected workspace is invisible | Open it in Notion as the same account; if you cannot, ask the page owner for access |
| Copilot will not update a Notion page | The federated connector is read-only, so no prompt will make it write |
| A second workspace shows nothing | It is a separate Notion authorization, not a permissions gap |
| Notion answers appear in one Copilot surface only | Federated connectors run in Copilot Chat, Copilot in Excel and the Researcher agent |
| No connector box anywhere in Copilot | Expected on both SKUs; the MCP surface is admin and maker gated |
Frequently asked questions
Can Copilot connect to two Notion workspaces?
No documented way exists. Notion issues one authorization per workspace and Microsoft exposes a single Connect action with no account picker, so you get one Notion slot.
Can Copilot write to Notion?
The federated connector cannot; Microsoft documents it as read-only. The Power Platform community connector has write actions, but it runs on a Premium licence in Copilot Studio and has no action for updating page properties.
Does the consumer Copilot at copilot.com support Notion?
No. Its connector list covers OneDrive, Outlook.com, Google Drive and Google Gmail, Calendar and Contacts. There is no personal-account route to Notion there.
Can I paste a connector URL into Copilot myself?
Copilot exposes no paste-a-URL box to ordinary users on either SKU. An administrator can add an MCP Base URL in the Microsoft 365 admin center, though those connectors are read-only, and a maker can add one in Copilot Studio, which is the route that carries write actions.
Does Copilot do anything when a Notion page changes?
No. There are no event triggers on any of the Notion paths, so nothing starts because a page was edited or a database row moved. Copilot answers inside a session you are driving.
Related: Microsoft Copilot and Notion · Multiple OneDrive accounts in Copilot · Best Notion integrations · Notion
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
