What the documents look like
Fresh-food supplier claims pursue quality liability for goods on arrival. They do not handle ordinary store shrinkage, which separates this category from markdown and near-expiry disposal work. The materials come from quality inspection systems, warehouse receiving records, supplier contracts and finance reconciliation. Day-to-day documents include quality exception notes, photographic evidence, deduction notices and claim reconciliation statements. Updates arrive per batch and per month.
For contract and transaction material comparison, the practical difficulty is that contract terms, receiving records and claim documents sit in different sources while a comparison has to place them inside one authorized scope. The access boundary decides which members can see which batches and which fields. A comparison result is only meaningful when the person running it can actually read every document being compared.
Constraints at the access controls step
Knowledge base permission is a threshold. Collection permission cannot bypass knowledge base permission: a member granted access to a single file still needs read permission on the knowledge base that contains it. When file-level permission is off, collection readability follows the knowledge base exactly and the system queries no collection permission records. When it is on, each file and folder carries a permission snapshot, and list views, detail views and retrieval recall are each checked against that snapshot.
Retrieval recall filters by the files the current member can read only when authentication runs under the current member identity. A workflow that preselects a knowledge base without member-identity authentication does not apply file-level filtering and still recalls by knowledge base permission. A team administrator does not bypass file-level permission; knowledge bases and files remain governed by their own collaborator configuration. Retrieval relevance is not a permission filter or an entity filter, and a similarity setting does not exclude unrelated businesses or unauthorized records.
Hypothetical paper exercise. In a fresh-food supplier claim scenario, the contract text supplied for comparison reads: "Party A purchases one batch of spinach from Party B on 1 March 2025; the acceptance standard is a leaf integrity rate of no less than 90%." The quality exception note reads: "Spinach arriving on 5 March 2025 measured a leaf integrity rate of 82% and was judged non-conforming." The draft sentence awaiting review reads: "Based on the contract and the receiving record, this arrival is non-conforming and a deduction is proposed." The draft sentence involves a subject, an object and a status, and it must be checked under an account holding knowledge base read permission plus read permission on the relevant contract and quality files.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | Reason for the choice and comparison method |
|---|---|---|
| Knowledge base file-level permission | On | Contract and quality materials need file-by-file isolation; compare visible list scope against the off state |
| Contract file collaborators | Purchasing member read permission | Purchasing needs to consult contract terms; compare visible content against the quality member account |
| Quality file collaborators | Quality member read permission | Quality needs to consult exception notes; compare visible content against the purchasing account |
| Claim reconciliation statement collaborators | Finance member read permission | Finance needs to check deduction amounts; compare access results against an account with no permission |
| Retrieval authentication mode | Current member identity | Compare recalled file scope against a preselected knowledge base without identity authentication |
These values are hypothetical starting points for this exercise, not official defaults. The entry point for turning on file-level permission is the menu on the target row of the file list on the knowledge base detail page, and the required permission is knowledge base manage. Collaborator configuration uses full-overwrite semantics, so the submitted list must contain the current creator. The creator cannot be granted or modified through collaborator configuration.
Three common errors
- Treating retrieval relevance as permission filtering. Input the same query and compare the recalled file lists of an authorized account and an unauthorized account, observing whether the unauthorized account still sees files it has no permission to read. Retrieval relevance carries no permission isolation.
- Treating a team administrator as exempt from file-level permission. Input a team administrator account against a file it has no permission for, compare the visible content with that of the file creator, and observe whether the administrator is stopped by file-level permission. A team administrator does not bypass file-level permission.
- Treating a deduction notice under review as an approved and executed deduction. Input the draft sentence together with the deduction notice, compare the notice status field against approval records, and observe whether any completed approval evidence exists. Pending review does not show approval.
How to verify the setup
- Input the contract text and the quality exception note from the hypothetical exercise, and search using an account that holds knowledge base read permission plus read permission on the contract and quality files. Compare whether the recall result contains both materials; the expected observation is that both appear in the readable list. If only one is recalled, record the missing item and check the collaborator configuration.
- Input the same query using an account without read permission on the contract file, and compare whether the recall list excludes the contract file. The expected observation is that the contract file does not appear in that account's readable results. If the contract file appears, record the unauthorized visibility and check the file-level permission switch and the collaborator list.
- Input the draft sentence "Based on the contract and the receiving record, this arrival is non-conforming and a deduction is proposed." Compare the acceptance standard in the contract text against the measured value in the quality exception note, and observe whether both point to the same batch and the same conclusion. If the contract does not state that batch or that acceptance standard, record the sentence as unsupported and keep the evidence gap open. A judgment requires the same subject, the same period and the same field; only mutually exclusive values in the same field count as a contradiction, and a stage showing only related evidence remains unsupported or pending verification.