updates.humandnai.xyz
← Back

How to Use Multiple Knowledge Bases in dnAI Without Mixing Brands or Losing Context

How-To

How to Use Multiple Knowledge Bases in dnAI Without Mixing Brands or Losing Context
SUMMARY: dnAI’s Multi‑Knowledge Bases keep brands, assets, and context fully isolated by letting you work in one clearly defined active Knowledge Base at a time. By selecting the right active KB before chatting, uploading, saving, or running workflows, teams create and automate content with confidence without cross‑contamination.

Who This Is For

  • Customers on the Custom tier working across multiple brands, products, or teams.
  • Content, brand, or operations teams who need clear separation of context.
  • Agencies managing more than one client inside the same dnAI environment.

The Problem (Why This Matters)

When working across brands or use cases, uncertainty can arise. You may hesitate before uploading, double-check before saving, and wonder whether dnAI is pulling the right voice, facts, or assets.

Multi‑Knowledge Bases exist to provide clarity. Each brand or initiative gets its own space, ensuring dnAI always knows which context to use, eliminating the need for mental management.

What You’ll Achieve by the End

  • Understand what a Multi‑Knowledge Base is and how it works.
  • Clearly grasp the concept of an active Knowledge Base.
  • Know how to switch contexts without risking cross‑contamination.
  • Create, save, and automate content with confidence.

Step‑by‑Step Instructions

Step 1: Understand What a Multi‑Knowledge Base Is

A Multi‑Knowledge Base setup allows you to work with separate, isolated knowledge spaces inside dnAI.

Each Knowledge Base has its own:

  • Documents and uploads.
  • Website crawls and style guides.
  • Saved outputs from chat, research, and workflows.
  • Images and brand assets.

Nothing automatically carries over; each Knowledge Base is its own source of truth.

Step 2: Understand What “Active Knowledge Base” Means

Your active Knowledge Base is the one dnAI is using at any given moment.

A simple way to think about it:

  • You can have many Knowledge Bases.
  • You can only work inside one at a time.
  • The active Knowledge Base defines the context for everything you do.

When a Knowledge Base is active:

  • Chat answers pull from that Knowledge Base only.
  • Uploads and crawls save into that Knowledge Base.
  • Saved outputs are stored in that Knowledge Base.
  • Workflows use that Knowledge Base for context unless explicitly configured otherwise.

Changing the active Knowledge Base changes the entire working context.

Step 3: Select Your Active Knowledge Base

Once Multi‑Knowledge Bases are enabled on your account:

  1. Look at the dashboard header.
  2. Open the Knowledge Base dropdown.
  3. Select the Knowledge Base you want to work in.

Your selection persists across sessions. When you return later, dnAI remembers your last choice.

A useful habit is to glance at the header before starting any meaningful work.

Step 4: Use Chat With Confidence

When you ask dnAI a question:

  • It uses only the active Knowledge Base for context.
  • Sources shown in responses come from that Knowledge Base.
  • Regenerating a response uses the same Knowledge Base as the original.

This keeps voice, facts, and tone aligned without extra instructions.

Step 5: Upload and Ingest Content Intentionally

Before uploading files or crawling a website:

  • Check which Knowledge Base is active.
  • Confirm it matches the brand or use case you are working on.

Uploads, crawls, and extracted style guides always save to the active Knowledge Base.

Step 6: Save Outputs Without Worry

Any time you save content in dnAI, it saves to the active Knowledge Base:

  • Chat responses.
  • Guided Prompts.
  • Deep Research.
  • Brand Monitor outputs.
  • Content Architectures.
  • Workflow results.

Saved content always stays with the context it was created in.

Step 7: Work With Images and Brand Assets

Visuals follow the same rule:

  • The image picker shows assets from the active Knowledge Base only.
  • Generated images save to that Knowledge Base.
  • Brand visuals remain isolated per Knowledge Base.

This protects visual identity just as carefully as written voice.

Step 8: Use Workflows Thoughtfully

By default:

  • Workflows use the active Knowledge Base for context.
  • Each execution records which Knowledge Base was used.

Advanced workflows can:

  • Always use the Primary Knowledge Base.
  • Follow the active Knowledge Base.
  • Be locked to a specific Knowledge Base when accuracy matters.

What Stays Shared Across Knowledge Bases

Some elements are intentionally client-wide:

  • Your Learning Profile, which always lives in the Primary Knowledge Base.
  • User accounts and permissions.
  • Workflow templates and schedules.
  • External API access, which uses the Primary Knowledge Base.

This balance keeps governance simple while content remains separated.

Common Mistakes to Avoid

  • Forgetting to check the active Knowledge Base before bulk uploads.
  • Switching Knowledge Bases mid-task without noticing.
  • Assuming dnAI will infer the correct brand automatically.
  • Treating Knowledge Bases like folders instead of isolated systems.

Optional: Pro Tips

  • Name Knowledge Bases clearly, for example “Brand A, Marketing” or “Brand B, Support”.
  • Add short descriptions so teammates understand the purpose instantly.
  • Keep shared foundations in the Primary Knowledge Base.
  • Make checking the active Knowledge Base a natural pause point in your workflow.

Simple Checklist

  • Active Knowledge Base confirmed in the header.
  • Correct Knowledge Base selected before uploading or saving.
  • Chat sources reviewed for context accuracy.
  • Workflow Knowledge Base settings checked when precision matters.
  • Team aligned on when to use each Knowledge Base.

Final Thought

When the active Knowledge Base is clear, everything else becomes easier. Your thinking stays focused, your work remains clean, and dnAI consistently supports the brand or idea you are working on in that moment.