Assign knowledge to the right agent
Scope each agent to the knowledge sources it should be allowed to retrieve.
2 min read
- Project
- Assistant
- Knowledge
Open the assistant that should use the material, then use its Knowledge tab to select from the ready sources in the shared project library.
Keep public-facing assistants narrow: assignment decides what a ready source is allowed to inform.
- Finish with
- Each agent retrieves only its approved knowledge
Decide the access modelDefault is broad; explicit selection is safer for specialized workflows.
When no agent selection is supplied, a new source goes to all active agents. Choose an explicit set for one workflow; an explicit empty selection leaves it unassigned. For example, warranty rules go to Support, product guides to Sales, and unreviewed internal escalation text to neither public agent.
Save the agent’s source selectionUse the agent’s Knowledge tab to turn sources on and off.
Open the agent’s Knowledge tab, make the selection, and save it. An existing assistant can be left without sources. Removing a native store source first explains that its store answers and shopping help will stop; confirm that effect only when intended. Selecting the website assistant in Integrations attaches the same shared source. Ordinary connection saves do not undo a deliberate removal.
Prove the boundary worksReady and assigned are both required.
Confirm selected sources are Ready, then test a realistic question. Current assignments govern new source-backed answers, restored store context and shopping actions. Removing access does not make unready content usable or recall information a visitor already saw. Use coverage and cited-source views where available as operational evidence, not proof of correctness.
Last updated on