Skip to main content
Knowledge is your company’s base of documentation and definitions, inside Cortex. Instead of knowledge being scattered across drives, PDFs and people’s heads, you keep it here — and the agents start answering based on it, with a link to the source.
Knowledge base

📸 Screenshot to insert [/en/cortex/knowledge]: Knowledge page with the Pages tree on the left, the list of documents by area, the glossary and the 'New page', 'Note', 'Term' and 'Upload' buttons.

​
How it works, in one sentence

You write Pages, add documents and glossary terms → iTeam indexes the content by meaning → when an agent (or Cortex) needs it, it searches, uses and cites it — respecting the permissions of whoever asked.

​
Three things you keep here

Pages

Your company’s living documentation: policies, playbooks, procedures. Full editor (headings, lists, tables, images, callout panels), sub-pages, version history and AI writing alongside you.

Documents and files

What already exists: PDF, spreadsheet, deck, pasted text. You upload the file and iTeam extracts the content.

Glossary

Your company’s/industry’s terms and acronyms, with definitions. E.g. in iGaming: GGR, NGR, FTD, MTD. That’s how the agent speaks your language.

​
Pages: living documentation

A Page is the document your company reads every day — the refund policy, the onboarding walkthrough, the sales team rules. Click New page and start writing.
Page editor

📸 Screenshot to insert [/en/cortex/knowledge]: full-screen Page editor, with the title as H1, the formatting bar, the side outline and the 'Write with AI' panel open.

​
Every page has an address

A page is not a dialog: it’s a screen with a link. The address shows up in the browser bar — you can send it over chat, paste it in meeting notes, bookmark it, open it in another tab. The reading screen gives you back, a clickable trail up to the parent page, an outline that jumps straight to a section, sub-pages and related pages as links, a copy link button, the history, and Edit (which edits at the same address). Documents, files and glossary terms have their own screen too.

​
The editor, for non-technical people

  • Plain-language formatting: bold, italic, headings, lists, task lists, quote, code, divider, link.
  • Images: drag them in, paste (Ctrl+V) straight from a screenshot, and drag the edge to resize.
  • Tables with header row, add/remove row and column.
  • Callout panels (tip, info, warning, success, error) for what must not be missed.
  • Automatic outline built from the headings — the page navigates itself.
  • / menu: type / mid-text and pick a block (heading, table, image, panel, list…).
  • Copy and paste from outside keeps the styling (bold, lists, links, tables).
  • Local draft on every keystroke: if the browser closes, your text is there when you come back.
A page only enters search and agent answers once it is Published. While it’s a draft, it’s yours to work on in peace.

​
AI writes with you — and you say what you want

The AI button at the top of the editor opens the writing panel. The important part: there’s a field where you say what you want, in plain language — “focus on the sales team, include a table of minimum office days and an equipment checklist” — and the AI follows it.
1

Outline

Give the subject and the instruction. The AI proposes a title + sections, already formatted and consistent with what’s already documented in your company (it reads Knowledge before writing).
2

Section by section

Ask for one section at a time (“Office days”, “Exceptions”). The AI writes just that block and drops it in place — you review and move on.
3

Improve what's already written

Select a passage and ask to improve, shorten, expand, or turn it into a list/table, with whatever tone instruction you want.
The AI uses the platform model and never publishes for you: the text lands in the editor as a proposal — you review and publish.

​
Organization: tree, sub-pages and labels

  • Sub-pages (up to 4 levels): click + sub-page in the tree. Great for “Sales handbook → Prospecting → Contact cadence”.
  • Drag to move a page to another parent or another position.
  • Labels (e.g. policy, onboarding) to filter the tree.
  • Page mentions: type @ and the title to create a link between pages. Each page shows who cites it.

​
History and periodic review

Every publish creates a version with author and date. You open the history, compare and restore any earlier version — nothing is lost. You can also set “review every N days”. Once the deadline passes, the page is flagged as may be out of date and the owner is chased automatically until they click reviewed.
The “may be out of date” flag is visible to readers and is taken into account by the agents: they warn you the source is overdue instead of answering as if it were fresh.

​
On mobile

On the phone the page fills the screen below the app bar, with the formatting bar scrolling horizontally, the AI panel rising as a bottom sheet, and the same save draft, publish, history and access buttons.

​
Adding a document or a file

1

Pick the area

Every item belongs to an area (e.g. Marketing, Finance). That organizes the base and controls who sees it.
2

Upload or write

Upload a file (iTeam extracts the text) or write straight in the editor. Give it a clear title — that’s what search leans on later.
3

Set who can read it

Company, area, chosen people, or only you (see below).
On save the content is indexed (turned into a representation the AI searches by meaning). Large items may take a few moments to become 100% searchable — the title is available immediately.

​
Who can read it: the four options

The access button in the page editor (and in the document form) offers exactly the same four options for every kind of content:
The rule covers reading, search and the agents — it is enforced inside the search mechanism itself, not just “hidden in the UI”. What you restrict here does not show up in the answers of anyone without access.

​
How the agents use it

When you ask an agent (or Cortex, or your Personal Assistant) something, it searches Knowledge and answers with the relevant passages, citing the title. When the source is a Page, it hands you the page link — one click and you’re in the document. The agent can also propose documentation: ask “document this as a page” and it creates the page as a draft, with the link, for a human to review and publish.
Start with your industry glossary and 2 or 3 key pages (support policy, business rules, one playbook). The payoff shows up in the very first conversation with an agent.

​
Search by meaning

Search is semantic: you don’t have to guess the exact word. Asking “what’s our discount limit?” finds the right passage even if the page says “commercial concessions policy”. The type filter includes Page, alongside documents, files and glossary.

​
Same thing in a project — and isolated

Every project has its own Project Cortex with its own Pages tab. It works the same way, but the content is isolated: a project page is only read by project members and only used by that project’s agent.