Knowledge

Knowledge is a shelf of documents for your project, written in Markdown: how an “active user” is defined, how revenue is counted, where a dataset comes from, how to read a dashboard. Everyone in the project can read them. Editors and admins write and edit them.

The Agent reads these documents too, so writing a definition down once makes its answers match how your team talks about the numbers.

Finding things

The list works like Dashboards: sort by last opened, recently updated, recently created or A to Z (remembered for you), and search titles and text.

Writing a document

Press + New document (editors and admins). Give it a title and write in Markdown; the Preview tab shows how it will look, and on wide screens it sits beside the text. Save with the button or ⌘S / Ctrl+S.

You can also Upload .md to start from an existing file (the title is taken from its first heading if you haven’t typed one), and Download .md on any document.

Markdown you can use

You type	You get
`# Heading`, `## Smaller`	headings
`bold`, `italic`, `code`	bold, italic, `code`
`- item` or `1. item`	lists
`[text](https://…)`	a link (web, email or in-app addresses only)
`> note`	a quote
a `\|`-separated table with a `---` row	a table
a fenced block of three backticks	a code block
`![alt](https://…)`	an image (https only)
`---` on its own line	a divider

A document can be up to 200,000 characters, and a project can hold up to 500.

Good things to write

Definitions of your key metrics and dimensions.
Rules: which traffic to exclude, how time zones are handled, what “revenue” includes.
How-tos for your team’s recurring reports.
Data notes: known gaps, when something changed, who owns a source.