Skip to main content
This feature is under active development. Details on this page may change.
Knowledge documents are contextual documentation attached to projects that help Addison understand your data and business domain. They enrich the catalog and improve the quality of Addison’s results.

​
What to include

Good knowledge documents cover things that aren’t obvious from the raw data:
  • Metric definitions — how your organization calculates revenue, churn, LTV, etc.
  • Business glossary — terms and acronyms specific to your domain
  • Data quirks — known issues, exclusions, or special cases in your data
  • Domain context — how your business works, what matters, and why

​
Adding knowledge to a project

  1. Open a project
  2. Go to the Knowledge section
  3. Upload or create a document
Knowledge documents are scoped to the project they’re attached to. When Addison works in that project, it has access to the knowledge context.
Screenshot needed: Adding a knowledge document to a project

​
How it helps

Without knowledge documents, Addison relies on table names, column names, and your catalog to understand your data. Knowledge documents fill in the gaps:
  • “Revenue” means net revenue after refunds, not gross
  • “Active user” means logged in within the last 30 days
  • “Region” column uses internal codes — NA = North America, EMEA = Europe/Middle East/Africa
  • Q1 starts in February for this business (non-calendar fiscal year)
The more context you provide, the fewer corrections you’ll need to make.