KorinAI

Feeding Knowledge

Enhance your assistant with files and notes as system knowledge base — agents automatically search enabled knowledge by intent, so there’s no need to attach sources in chat.

Overview

Attach files (media/documents) and author notes as knowledge sources. During conversations, the assistant uses these sources to ground its answers with your materials.

Concepts

  • Knowledge Source: A file (from Gallery) or a text note.
  • Visibility: Public (available broadly) vs Private (restricted to an allowlist).
  • Knowledge Toggle: For files, the 📚 icon marks whether a file is part of the knowledge base.
  • Grounded Answering: Prompts can ask the assistant to use a specific note/file or the knowledge base in general.

Step-by-step — Dashboard flow

  1. Login.
  2. In Chat dashboard, select your agent → click the gear icon (Settings).
  3. Open the Knowledge tab. You’ll see two sub-tabs:
    • Text Knowledge
    • File Knowledge
  4. Add knowledge:
    • Text: click Add, write content, set visibility (Public/Private), save.
    • File: upload in Gallery, toggle 📚 to include, set visibility.
  5. Organize:
    • Search filter, pagination controls.
    • Click to view/edit; delete with confirmation.
    • Badges: 🌐 Public, 🔒 Private; a “shared” badge shows private allowlist count.

Managing Knowledge

Gallery Files (media/documents)

  1. Dashboard → Gallery → Upload files.
  2. Toggle the 📚 icon on a file to include/exclude it from the knowledge base.
  3. Set visibility:
    • 🌐 Public – visible to all authorized contexts.
    • 🔒 Private – add specific emails to allow access.
  4. Use search and type filters to manage items.
  5. From the agent Settings → Knowledge tab (File Knowledge), you can also quickly review items and their visibility.

Knowledge Notes (text)

  1. Settings (gear) → Knowledge tab → Text Knowledge → click Add.
  2. Enter a clear title; write content (markdown supported).
  3. Optionally import captions from Gallery files.
  4. Set visibility and update allowlist for private notes.
  5. The list view supports:
    • Search field for quick filtering.
    • Click to view/edit a note (detail view), with a back button to return to list.
    • Delete action with confirmation.
    • Pagination controls if there are many items.

Using Knowledge in Chat

Use knowledge to ground responses and improve accuracy. By default, your agent will automatically search across enabled knowledge (Text and File) based on the user’s query intent—no manual attachment in chat is required. You can optionally scope sources, request citations, and combine internal knowledge with external tools when enabled.

Scoping what the assistant can use

  • Optional scoping when you want tighter control:
    • “Answer using ‘onboarding.pdf’ only.”
    • “Compare ‘policy-v2.pdf’ with the note ‘Policy Summary’.”
  • Allow any internal knowledge (default behavior):
    • “Use our internal knowledge base if relevant, and cite what you use.”
  • Disable internal knowledge (for a query):
    • “Ignore internal knowledge and answer generally.”

Citations and evidence

  • Ask for citations explicitly: “Cite from internal notes with filenames/titles.”
  • The assistant should reference file/note names and, when possible, relevant sections or headings.
  • If an answer cannot be grounded, have it state limitations (e.g., “No matching internal sources found”).

Precedence and combination with tools

  • Internal knowledge typically takes precedence for organization‑specific facts.
  • When research tools are enabled (e.g., web search/crawl), the assistant may augment answers with public sources. Clarify your intent:
    • “Use internal knowledge first; add public sources only if we lack coverage.”
    • “Only use internal knowledge; do not add external links.”

Privacy and permissions

  • Private items are only usable when the current user/email is on the allowlist.
  • If an item is not accessible, the assistant should proceed without it and may explain that a private source was unavailable.

Examples

text
“Summarize the Onboarding Guide. List sections and open action items. Cite the file.”

“Create a FAQ from ‘Support Notes’ and ‘Troubleshooting.pdf’. Include source references.”

“Draft a release note using ‘Release Plan Q3’. If anything is missing, list open questions.”

Tips

  • Name files/notes clearly so you can reference them by title.
  • Keep notes focused; small, specific sources ground better than one large dump.
  • When you need both internal and external context, say so explicitly.

Troubleshooting

  • “The assistant ignored my file”
    • Ensure 📚 is toggled on for the file and it’s Public or your email is on the Private allowlist.
    • Reference the exact title used in the Gallery/Knowledge list.
  • “No citations included”
    • Ask for citations explicitly and specify the format (filenames/titles/sections).
  • “Mixed internal/external content unexpectedly”
    • In your prompt, state “Use internal knowledge only” to prevent external tools.

Best Practices

  • Use descriptive titles and keep notes concise but complete.
  • Group related content and use consistent naming for easy discovery.
  • Review visibility and access lists regularly, especially for private data.
  • Prefer smaller, focused notes over one giant document for better grounding.

Related Topics

Previous
← Introduction
Next
Built-in Tools →