Why it matters
Every AI answer ultimately depends on upstream sources someone must own. Source management assigns that ownership, documents dependencies, and schedules reviews across Help Center, policy hubs, and PDFs.
How it works
Maintain a source catalog: URL, owner, collections fed, apps affected, review cadence. Onboard new sources through verification before indexing.
Example
Nintendo source catalog lists the Refund Policy hub owned by legal, synced daily, feeding public chatbot and docs assistant collections with quarterly review.
Common mistakes
- 1Shadow sources indexed from personal drives
- 2No owner for attached PDFs linked from Help Center
- 3Sources added without mapping to collections
Your source changed. Your AI should know.
Track source freshness, detect changes, and review impact before answers drift.
Explore Source Maintenance