Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.teeem-ai.com/llms.txt

Use this file to discover all available pages before exploring further.

The fastest way to stop employees from rummaging through the company wiki. With 10–20 core documents, immediate value.

​
What you get

An employee asks in Slack or web chat: 
@Teeem What's our hotel limit for business travel?
Teeem AI answers: 
For travel within Seoul / metro area, the hotel limit is ₩200,000/night;
for other regions, ₩150,000/night (Travel Policy, Article 5, Clause 1).
Exceeding the limit requires advance approval from your department head.

─── Sources ───
📄 travel-policy-v3.pdf (updated 2026-03-15)
   page 4, "Article 5 Limits"
Employees stop searching PDFs and stop pinging HR.

​
30-minute setup

1

1. Identify core documents (5 min)

Quality of the KB is everything. List the top-10 questions employees ask, then collect the documents that answer them.Examples:
  • Travel policy → travel-policy-v3.pdf
  • Vacation policy → vacation-policy-2026.pdf
  • Expense handling → expense-handbook.pdf
  • Approval flow → approval-flowchart.pdf
  • Internal system manuals (Wehago, Douzone)
Group by department: HR / Finance / Legal / IT.
2

2. Bulk upload to KB (10 min)

Admin console → Knowledge Base → Upload → drag a folder.Per file:
FieldValue
DepartmentHR / Finance / Legal etc.
Sensitivitypublic for general, internal for HR policy, secret for executive comp
Tagspolicy, manual, 2026
Languageko
Three-tier dedup prevents double-indexing if a file is uploaded twice.
3

3. Verify with real questions (5 min)

Ask 3–5 questions employees actually ask:
@Teeem What's our hotel limit on business travel?
@Teeem How do I check remaining vacation days?
@Teeem How do we handle corporate-card overages?
@Teeem How to submit an approval in Wehago?
@Teeem Vacation policy if I'm Covid-positive?
For each answer, verify:
  • Accuracy (compared to the source PDF)
  • Citation points to the right page
  • Sensitivity classification is right
  • For unknown questions, the agent says “no source found” honestly
4

4. Tighten answer policy (5 min)

For high-stakes channels (e.g. #legal), force citations.Admin console → Operations → Answer policy:
require_citations:
  - channel: "#legal"           # No citation, no answer
  - channel: "#hr-policy"
  - role: "viewer"              # Viewers see only cited answers
Details on the Citations page.
5

5. Tell your employees (5 min)

The key: value only emerges if employees use it.
  • Internal announcement: “Now ask @Teeem in Slack about policies”
  • Five usage examples on the company wiki / intranet
  • Demo at the next manager all-hands
Measure impact:
  • Number of policy questions HR receives → before/after
  • Wiki page views → before/after

​
Document lifecycle

Policies change. The KB doesn’t need to be hand-maintained.
SituationWhat happens
Policy revision (v3 → v4)Upload new PDF → auto-supersede → v3 dropped from search
Policy retirementMark archived in admin console → excluded from search, audit trail preserved
Sensitivity changepublic → private → change history recorded automatically
Department transferEdit department metadata → ACL re-applies automatically
See Knowledge Base for details.

​
Common gotchas

The PDF’s text is too short, or information is locked in tables/images. Verify text extraction. Scanned PDFs without a text layer get OCR but with reduced accuracy.
Upload the new version to trigger supersede. The old version drops out of search automatically. Verify in the version history panel.
Sensitivity probably set to public by mistake. Change to private immediately. The audit log captures everyone who accessed it.
Possibly conflicting policies in different documents. The KB usage statistics page surfaces frequently conflicting documents — clean those up.

​
Next

Weekly report automation

Build scheduled reports.

Data analysis automation

Pile of Excel → insight.