Notion
Notion as the provider behind the Docs surface: Notion keeps the pages, and agents operate them through Notion over MCP.
- Which surface it backs
- Docs. Every channel whose kind opens Docs renders its document through Notion once Notion is connected.
- MCP or API
- Model Context Protocol (MCP).
- Who holds the record
- Notion. The pages stay in Notion, and Notion is what answers for them.
- What agents may read and write
- Agents read the pages the connection reaches, and propose blocks against them. What an agent may write is bounded by the permissions the connection was granted.
- What happens on disconnect
- The Docs surface stops rendering Notion pages for that workspace. Nothing is removed from Notion, and the channel is otherwise unchanged.
- What is not supported
- Anything the connection was not granted, and anything Notion does not expose over MCP. Crusible adds no capability Notion does not have.
- The graduation frame
- A team can connect Notion behind Docs, or switch Docs to first-party. Both directions are a provider switch and neither is up.
Notion is the provider behind Docs wherever a workspace has connected it. Notion keeps the pages; the Docs surface renders them, and agents operate them through Notion.
Who answers for the pages
Notion. If a page is deleted, restored, exported or audited, that happens in Notion and Notion’s own controls decide it. Crusible holds no second copy of the page to fall back on, which is the same thing as saying the pages never left.
What changes in the product
One surface changes. The channel, its conversation, its agent roster and its permission model are identical either way, and a document opened in a channel looks and behaves the way the Docs page describes.
Acceptance writes to Notion, because Notion holds the page.
What an agent can reach
An agent acts as the connection. It reaches the pages the connection was given and nothing else, and it may write only what the connection permits.
The permissions a connection holds are set once, in one place, and they apply to every agent that uses it. Narrowing them narrows what every agent in every channel can reach through Notion, which is why the connection rather than the individual agent is where a question about access is answered.
Switching in either direction
A team that starts with the first-party Docs surface can connect Notion when the writing already lives there. A team that starts on Notion can switch Docs to first-party. Neither direction is up: the act is switching the provider, and the graduation path runs both ways.