Organisational memory the AI can actually use.
A wiki where pages link to the records they describe. Public articles drive the customer portal KB; internal articles ground every AI answer in your own knowledge.
A live product capture for this area is not published yet — we only show screenshots of the running app.
What Docs does for you
Pages, spaces, search
Standard wiki shape. Rich text, tables, code blocks, mentions, and full-text search out of the box.
Linked to records
Mention an account, a deal, or a project, and the page becomes a node on the graph. Show up against the record automatically.
Powers the AI
Internal docs are RAG sources for every Cyril agent. Update a doc, agents update their answers — no retraining, no fine-tuning.
Permissions you control
Page-level visibility: org-wide, team, or specific roles. Public pages render on the customer portal; private ones never leave the org.
AI answers are only as good as what you write down.
Most "AI assistants" hallucinate because they don’t have your team’s tribal knowledge. Cyril’s Docs module is where you write that knowledge once — and every agent in every module immediately uses it.
- Update a doc → every agent’s answer updates
- Public pages drive the customer KB
- Mention syntax (`@account/Acme`) creates real graph edges
Update a page and every agent’s answer updates with it.
Internal docs are retrieval sources for every Cyril agent, so the knowledge base and the AI’s knowledge are the same thing rather than two copies that drift. No retraining and no fine-tuning is involved — and page-level permissions still apply, so an agent cannot surface a page the person asking could not open themselves.
- Docs are the retrieval source, so there is one version of the truth
- Page permissions bind the AI exactly as they bind a person
- Public pages render in the customer portal; private ones never leave
Common Docs questions
Bulk import from Markdown and HTML is on the Phase 4 roadmap. Confluence and Notion-specific importers are planned but not yet shipped.
For pages, spaces, mentions and search over your own records, yes. For deep publishing workflows — editorial approval chains, versioned public documentation sites — a dedicated product will do more. The trade is that a dedicated product’s pages are not on the graph your AI reads.
Page-level visibility: org-wide, a team, or specific roles, running off the one permission model rather than a docs-specific sharing scheme. That is also what makes the retrieval answer above safe.
No. Linking makes the page appear against the account, deal or project it describes; it does not widen access. A reader who cannot open the page does not see it listed against the record either.
Be one of the first to use Cyril.
Join the waitlist for early access. We'll only email you when there's something real to share.