What this category of data looks like
Data for the internal system and data Q&A scenario of permission-controlled file isolation mainly comes from internal official documents and structured business attachments (such as CSV-format business ledgers) of state-owned enterprises, government agencies, and public service departments. Update frequency aligns with system revision cycles, or is triggered temporarily by changes to business data. Individual documents include fields such as system text, permission hierarchy tags, attachment data, update time, and responsible management department. File size is measured in MB, content length is measured in characters, and permission scope is identified by job or department names.
Constraints on citation sources and traceability
The permission hierarchy tags of internal systems require verifying the visitor's permission scope during traceability, to prevent unauthorized access to sensitive content. CSV-format business attachments require correct encoding parsing. Incorrect parsing causes content garbling, which affects traceability accuracy. The non-fixed update frequency requires traceability results to match the latest version of file content in real time. A large number of structured attachments leads to a large volume of citation content per search round. Reasonable control of context length is required to avoid exceeding the large model's processing limit.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value Range | Rationale |
|---|---|---|
quoteMaxToken | 8000–12000 token | Internal system documents have long individual content; this ensures complete transmission of core citation content to the large model and avoids context truncation |
responseData | Standard structured JSON | Internal CSV attachments and business data require standardized conversion to be properly indexed by the knowledge base and meet traceability requirements |
detail | Enabled | Permission-controlled file isolation scenarios require clear display of the permission scope and update time of cited files to meet compliance traceability requirements |
| File Encoding | UTF-8 | UTF-8 is a common encoding for internal CSV files, which can avoid garbled characters after upload |
| Single Recalled Citation Count | Top 3–5 entries | Internal system content is focused; excessive citations lead to redundant context and affect the accuracy of large model responses |
Three common misconfigurations
- Phenomenon: CSV files display garbled characters after upload, and no results are returned when calling the knowledge base search. Cause: The correct file encoding format is not specified, causing the knowledge base to fail to parse CSV content correctly.
- Phenomenon: After setting
quoteMaxTokento 3000, the large model cannot receive context content. Cause: The individual content of internal system documents exceeds 3000 tokens, and the small configuration value causes core citation content to be truncated and cannot be transmitted to the large model. - Phenomenon: Configuring citation sources has no effect, and file traceability information cannot be displayed. Cause: The
detailswitch is not enabled, or the response data format is not configured as standard structured JSON, causing traceability metadata to not be extracted correctly.
How to confirm the configuration is correct
- Upload a test internal system CSV file, check that the file content displays normally without garbled characters, to confirm the encoding configuration is correct.
- Initiate a knowledge base search, check whether the returned results include metadata such as the permission scope and update time of the cited file, to confirm the
detailswitch is enabled. - Adjust the value of
quoteMaxToken, test whether the large model can receive complete context content, to confirm the configuration value matches the content length of individual files. - Call the API with the knowledge base ID, check whether the workflow can correctly associate with the specified permission-controlled file isolation knowledge base, to confirm the global variable configuration is correct.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.