Upload, Search, and Use Knowledge Documents
Detailed guidance on supported formats, processing status, search methods, and how to use documents as evidence in projects.
Knowledge documents are not immediately usable after upload; they must undergo file validation and content processing before becoming searchable. This document explains the detailed flow from upload to result verification.
Supported Formats and Basic Limits
- PDF:
.pdf - PowerPoint:
.ppt,.pptx - Word:
.doc,.docx - Text:
.txt - Markdown:
.md - The default upload limit may be around 25 MB depending on operational settings.
- Corrupted files, password‑protected documents, and files whose actual format differs from the extension may be rejected.
Understanding Document Status
Processing Status
Pending
The file has been uploaded and is waiting in the processing queue.
Processing
The document’s text, pages, and search information are being prepared.
Completed
The document is searchable and can be referenced in projects.
Failed
The document failed due to format, size, corruption, network, or processing errors.
Uploading
- 1
Organize the files
Keep only the latest version and include content and reference timestamps in the file name. Check scan quality and page orientation.
- 2
Select files in Knowledge
Click the drop‑zone or drag and drop files. Multiple files can be selected, but uploading one file at a time is easier when diagnosing issues.
- 3
Check upload status
Verify that the file appears on the recent document card. Closing the file picker does not mean the upload is complete.
- 4
Wait for processing to finish
Processing may continue even if you navigate away. Reopen Knowledge to confirm the completed status.
- 5
Verify with a simple search
Ask a core question about the document and confirm that the answer matches the original text. If the required page is only an image, check OCR quality separately.
Searching
Searching is better suited for questions about document content than for finding by file name.
Good examples:
- “What were the most frequently mentioned adoption barriers, other than price, in the customer interviews?”
- “List the major milestones and responsible teams for the 2026 launch plan in chronological order.”
- “Identify the types of content that are prohibited from external sharing in the uploaded policy document.”
- “Summarize the three value propositions that are emphasized in both the sales materials and the product roadmap.”
Less good examples:
- “Summarize.”
- “Important stuff.”
- “Revenue.”
- “What was that document?”
Using for Deck Creation
Specify the scope of Knowledge usage in the project prompt like this:
Use Knowledge’s customer interviews and product roadmap as primary evidence. Use the pricing policy document only for background reference, and do not use any material from before 2025.
In subsequent revisions, narrow the target and source further.
Replace the evidence for slide 6 with the content from Knowledge’s `2026_customer_interviews`, and use only expressions that were actually repeated in the interviews.
When Documents Grow
- Use file names that distinguish older versions of the same document.
- Do not indiscriminately duplicate the same material in workspaces with different purposes.
- If older figures appear repeatedly in search results, instruct the prompt to prioritize the latest document.
- Separate external public materials from internal-only materials by workspace or access policy.
- If the recent document list alone is insufficient, use the document panel together with search.
If Rhetis does not specify which materials to use, multiple similar documents may be referenced together. It is important to note the reference document and the cutoff point for exclusion.