Scope
This guide covers daily operation for Knowledge Bases. Availability depends on your tenant package, role and configured providers.
Purpose
Ground people and AI workflows in managed source material.
Review documents, retrieval status and current guidance.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Review documents, retrieval status and current guidance.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Use approved knowledge in agents, chatbots and studio work.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Inspect source coverage, retrieval and evaluation context.
Verify the result
Inspect source coverage, retrieval and evaluation context. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Maintain provenance, access and superseded content. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.