See the complete route index at https://crusible.dev/llms.txt before following links. # Notion Notion as the provider behind the Docs surface: Notion keeps the pages, and agents operate them through Notion over MCP. 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.