Knowledge corpus

Your knowledge corpus is your organization's curated reference material. It helps supported AI workflows answer questions about your business using relevant information and citations.

Organization administrators manage it in Org settings → Knowledge corpus. The two tabs serve different purposes:

• Raw documents: source material, such as product documentation, pricing guidance, case studies, and extracted file text. These preserve the evidence behind your guidance.
• Derived documents: focused notes that turn those sources into useful guidance for Athean. Each has a title, a description explaining when it is relevant, content, and source citations.

For example, a product specification can be a raw document, while a note explaining how to answer a common buyer question can be a derived document that cites it. Adding source material and preparing the guidance Athean uses are distinct steps.

1. Open Org settings → Admin assistant.
2. Attach a supported source file, paste the material, or provide a public page URL. Supported file formats include PDF, DOCX, PPTX, TXT, Markdown, CSV, and HTML.
3. Explicitly ask to add the material to the knowledge corpus. Attaching a file to a conversation alone does not add it to the corpus.
4. Ask Athean to compare it with existing material and propose new or updated derived documents, with citations to the source.
5. Review the proposed changes and confirm the work you want it to perform. Check the resulting documents in Knowledge corpus.

Add this product guide to our knowledge corpus. Check for existing coverage, propose concise guidance for common buyer questions, and cite the source for each factual claim. Show me the changes before applying them.

A public URL can be fetched as source material. For a private content library or an ongoing connection to your internal documentation, chat with us about the setup.

Open Derived documents and select a note to read its guidance. Follow the citation markers to inspect the source material and the passage behind a claim. Use Edit and Save changes to update the note.

To write a note manually, choose New derived document. Add a clear title, a description of when it should be used, and Markdown content. Use Add citation to choose a raw document and provide the verbatim Cited text. Reference that citation in the content and review the rendered preview before creating the document.

For manual source entry, open Raw documents → New raw document. Add a title and the Extracted text. Paste text, From URL, and File reference all require that text. The URL and file-reference options record where the text came from; use the Admin assistant when you want a source fetched or a file ingested.

When source facts change, review the derived guidance that cites them. Updating a source does not guarantee that every note based on it has been rewritten. Check dependent citations before deleting source material.

A snapshot captures a version of the corpus. When your organization has an active snapshot, AI generation uses that published version. Saved edits become available to those workflows after a new snapshot is activated.

If no snapshot is active, generation uses the current saved corpus. Ask the Admin assistant to check which setup your organization uses before treating saved edits as unpublished drafts.

1. Ask the Admin assistant to compare your saved changes with the active snapshot.
2. Review the changed guidance, source citations, and any warnings about quotes that no longer match their sources.
3. Ask it to capture the reviewed corpus as a named snapshot, then explicitly confirm activation when you are ready to make that version available.

The document forms use Save changes; snapshot publication is managed through the Admin assistant. You can also ask it to review and reactivate an earlier snapshot when you need to return to a previous published version.

Try a real buyer question in a supported workflow, such as Ask knowledge base in Meeting assist, when available. Review the answer and open its citations. Check that the source supports the claim and that the advice reflects how your team wants to respond.

Athean selects relevant derived documents for the question; it does not include every source in every answer. If it reports missing coverage, add or improve the relevant material and check which version is active.

Keep the corpus focused on useful, current guidance: product capabilities, buyer personas, positioning, competitor comparisons, customer proof points, and your sales process. If the knowledge features you need are unavailable, chat with us about your workspace.