Browse docs

Knowledge bases

Upload brand guidelines, product documents and compliance material under Context so the assistant works from your business reality.

Knowledge bases hold the documents that make Morrison's answers specific to your business: brand guidelines, product sheets, compliance rules, research. Without them, AI answers are generic. With them, the assistant can tell you that a page breaks rule four of your tone guide.

Find knowledge bases under Context in the sidebar.

Why knowledge bases matter

Consider the difference:

  • Without context: "This page has a good structure."
  • With your brand guidelines: "This page uses 'cheap' in the headline, which conflicts with the premium positioning in your brand guide."

Creating a knowledge base

  1. Open Context in the sidebar
  2. Create a knowledge base and give it a clear name, such as "Brand guidelines 2026" or "Product feature matrix"
  3. Add documents to it

A knowledge base can have a type, such as Brand Guidelines, Product Information, Compliance Documents or Industry Guidelines, to keep things organized.

Adding documents

  • Upload: drop files on the knowledge base, or click Upload. Supported formats are PDF, DOCX, TXT and Markdown, up to 10 MB per file.
  • Add Content: write or paste text directly in Morrison. Pasting from a website or Google Docs keeps the formatting.

You can preview, download and delete documents at any time. Deleting a document also removes it from search.

How knowledge bases are used

In chat

The assistant can look through your knowledge bases and read the documents it needs. Ask, for example:

  • "Does our homepage follow our brand guidelines?"
  • "Which product pages are missing features listed in our feature matrix?"

In workflows

A Custom agent step in a workflow can use specific knowledge bases. Select them in the step's settings, and the step draws on the most relevant parts of those documents for each page. This is useful for:

  • Compliance checks: validate content against regulatory documents
  • Brand consistency: check that pages follow your voice and messaging
  • Product accuracy: verify that feature descriptions match current specs

How retrieval works

Morrison splits your documents into smaller sections and indexes them. When the assistant or a workflow step needs context, Morrison finds the most relevant sections and uses those. This keeps answers fast and focused, even with a large document library.

Knowledge bases, chat context or attachments?

  • Knowledge bases: long documents that should be available in every chat and workflow on the website
  • Chat context: a short note the assistant should always keep in mind
  • Attachments: a file you only need for one chat

Best practices

  • Keep documents focused: one topic per document helps the right section come up
  • Use descriptive names: for knowledge bases and documents alike
  • Keep them current: replace documents when they change
  • Start small: upload your most important documents first