CRUD: Training Documents and Knowledge Base
Property: ChurchWiseAI Category: Admin Dashboard
Tier:
pro-chat
Persona: pastor-admin
Touchpoint: /admin/[token]/training-tab
Preconditions
- Pastor logged into admin dashboard
- Training feature enabled (Pro tier or higher)
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Navigate to Training tab | Training tab loads. Shows sub-tabs: Documents, Website, FAQs. |
| 2 | Upload training document (PDF or Word) | Documents sub-tab has upload button. Can select PDF/DOC file. System accepts file and shows upload progress. |
| 3 | Verify document was indexed | After upload, document appears in list with status 'Processing' then 'Ready'. File size and upload date shown. |
| 4 | Preview document content | Can click document to see preview or extracted text. Confirms document was parsed correctly. |
| 5 | Delete training document | Can remove document from knowledge base. Confirmation popup. Once deleted, document no longer indexed for chatbot. |
| 6 | Add FAQ entries | FAQ sub-tab has form to add Q&A pairs. Can add multiple FAQs. Each FAQ saves individually. |
| 7 | Edit FAQ entry | Can update question and answer. Changes save and immediately available to chatbot. |
| 8 | Delete FAQ | Can remove FAQ entry. Confirmation prevents accidental deletion. |
| 9 | Link website to training | Website sub-tab allows pasting church website URL. System crawls and indexes pages as training data. |
| 10 | Monitor training indexing status | Progress indicator shows document indexing status. Can see which documents are ready vs processing. |
Known Failure Modes
- File upload fails for valid PDF — knowledge base can't be built
- Document indexed incorrectly — chatbot has corrupted data
- FAQ changes not reflecting in chatbot — stale answers
- Website crawl fails — churches can't use website as training source
References
- Playwright spec:
e2e/crud-admin-training.spec.ts - Code files:
Notes
Tests knowledge base creation and management. Training is the core of chatbot customization — documents, FAQs, and website content define how the AI responds. Uploads must work, indexing must be reliable, and pastors must see clear status. This is critical for pastor confidence in the AI's knowledge.